Jump to content

Search the Community

Showing results for tags 'dayz_code.pbo'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
  • DayZ
    • Discussion
    • Public Servers
    • DayZ SA Resources
    • Q&A Section
  • ArmA 3
    • Epoch Survival
    • Community Projects
    • Q&A Section
    • Terrain Discussion
    • Resources
  • Arma 3 Resources
  • ArmA 2
    • General Discussion.
    • Q&A Section
    • Resources
    • Legacy Resources
    • A2: Community Projects
    • A2 Community Servers
  • Space Engineers
    • General Discussion.
    • Public Servers
  • Other Games
    • Discussion
  • Off Topic
    • Off Topic

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Just_R

    variables.sqf

    I have a question or two. I watched a video by a well named person on these forums. He basically stated we can move things from the init.sqf into the variables.sqf thus eliminating double calls to the dayz_code.pbo. for example: spawnShoremode = 0; // Default = 1 (on shore) spawnArea= 800; // Default = 1500 DynamicVehicleDamageLow = 75; // Default: 0 DynamicVehicleDamageHigh = 100; // Default: 100 MaxVehicleLimit = 100; // Default = 50 MaxDynamicDebris = 0; // Default = 100 dayz_MapArea = 16000; // Default = 10000 MaxMineVeins = 1; MaxAmmoBoxes = 5;These above things can be stated at the beginning of variables.sqf, then repacked into the PBO. this being said, why can't we do this with compiles.sqf? fn_selfactions? etc? instead of copying these files to our MPMission folder plus the changes needed for the mod(s) -- so it ends up double calling things along with adding to an increased mission file?
×
×
  • Create New...