ArmA.PBO

 

RKSL-Arma.pbo was designed to allow all our current and future systems to be easily applied to vanilla ARMA addons and any other addon that inherits from them. In theory any mission that uses ARMA addons, can now take advantage of these features without having to be repacked.

But please bear in mind some mission may still need additional work or adjustment. If that is the case, we’ve added a variety of options and scripted functions to try and make life as easy as possible. All options can be configured through a mission’s description.ext file, by adding the appropriate entries.

So far the current systems supported are:

  • RKSL Cargo System (RKSL-CargoSys.pbo)
  • RKSL Chaff and Flares (RKSL-RadarSys.pbo

RKSL-Arma.pbo requires both the Cargo System and the Radar System addons to function. However you can turn either of them off if you want. As mentioned above this can be done for all vehicles in a mission, with description.ext. Or for individual vehicles, using functions.

* Server Admins: please read the Multilayer Compatibility section at the bottom of this page.

ArmA PBO Extension

ArmA PBO ExtensionArmA PBO ExtensionArmA PBO ExtensionArmA PBO Extension

 


 

Description.ext

Class NamePropertyValues
class RKSL_CargoSyscargosysonA value of 0 disables the Cargo System for the current mission. A value of 1 enables the Cargo System, overriding settings in the stringtable.
class RKSL_RadarSysradarflareonA value of 0 disables the Flare System for the current mission. A value of 1 enables the False System, overriding settings in the stringtable. Used in conjunction with mandomissileon=0 to disable Mando Flares and enable RKSL Flares.
 mandomissileonA value of 0 disables Mando Flares within A.C.E. A value of 1 enables Mando Flares within A.C.E. This value overrides settings made via the A.C.E interface. Used in conjunction with radarflareon=0 to enable mando Flares and disable RKSL Flares.

 

The following entered into a missions description.ext will, for the A.C.E mod. Disable Mando's Flares and enable the RKSL flares for all the default ARMA and A.C.E aircraft:

class RKSL_CargoSys
   {
   cargosyson=1;
   };

class RKSL_RadarSys
   {
   radarflareon=1;
   mandomissileon=0;
   };

 

For full details on the Cargo System Description.ext setting see here.

For full details on the Flare System Description.ext setting see here.

Example Missions

  1. rksl-arma-&-ace.Intro: A basic example mission showing how you can use rksl-arma.pbo to auto-inherit the Flare system functionality within A.C.E.
  2. rksl-description-ext.Intro: Example mission and description.ext for configuring the system settings and auto-inheritance with default Arma addons.

Functions

The following functions will come in handy for those occasions, where you want to remove functionality from specific objects. For example, you may want some ammo boxes setup around a spawn point. The last thing you want is for someone to drive off with them, loaded into the back of their truck. In which case, you can use the following functions, to remove the individual ammo boxes from the cargo system.


RKSL_SystemRemove

Removes the specified object from all RKSL systems.

[Object] Call RKSL_SystemRemove


RKSL_RemoveCargoSystem

Removes any cargo/transport properties from the specified vehicle or object.

[Object] Call RKSL_RemoveCargoSystem


RKSL_CargoRemove

Removes any cargo properties from the specified vehicle or object.

[Object] Call RKSL_CargoRemove


RKSL_TransRemove

Removes any transport properties from the specified vehicle or object.

[Object] Call RKSL_TransRemove


RKSL_RadarRemove

Removes the flares from the specified aircraft.

[Object] Call RKSL_RadarRemove


Addon Inheritance

As mentioned before RKSL-Arma.pbo applies all the current RKSL systems to the default Arma addons and those that inherit from them. A good example of this is A.C.E. When running A.C.E with the RKSL Cargo System, Flares and RKSL-Arma.pbo, any A.C.E object that inherits from the default ARMA addons will automatically be enabled with the RKSL System. So you will now be able to load the A.C.E Weapon and Medic boxes e.t.c onto any cargo compatible A.C.E transport.

The Flare system is a little more complicated. Because A.C.E already comes with Mando’s Flares, our Flare system is automatically disabled so as not clash with his. If you want to use our flares instead, you need to disable Mando Flares and enable RKSL Flares. See the description.ext settings mentioned above.

In some cases we can’t apply our system to inherited addons. The Cargo System requires a vehicles cargo proxies, to be placed in a specific way. For example any variation from the default Arma addons, even if it's just changing the proxy index, will break the Cargo System compatibility.

 

Multiplayer Compatibility

As mentioned above, rksl-arma.pbo allows you to apply RKSL scripts to any misson running units that inherit from default Arma addons. Without having to re-pbo the mission. But with regards to online games, we strongly advise you do re-pbo to ensure the correct dependancies are assigned, for the following reasons; Due to the way auto-inheritance works, it makes coordinating addons across public servers and clients a little more complicated. The only way to guarantee contenuity across the server and all clients is to use the following in your server.cfg:

  • equalModRequired=1;
  • verifySignatures=1;
However this is not always possible with public servers and players may want to browse different servers without having restarting Arma with different mod folders. With that in mind we have at least attempted to cover as many possibilities as we were able to. So for example, if you as a client, have rksl-arma.pbo and other RKSL addons installed. You can join any server regardless of whether it's running RKSL addons. Our auto inheritance is capable of detecting when your playing on a none RKSL server, so consquently turns off any RKSL functionality without disrupting the other players gaming.

Unfortunately the opposite scenario is not as easy to cope with i.e When the mission does not have the RKSL addon in thier required addons section. Anyone connecting to a server that's running rksl-arma.pbo in thier current mission without the correct dependancies, when they don't have any RKSL addons installed, will get the following error message:

 

Client Config Error

 

 

Again this won't disrupt the other players, the new client will not have access to any of the RKSL scripts or features. The worse that can happen is the clients AA missiles will not be subjected to the RKSL Flares. Please remember this will only happen when the server runs a mission with rksl-arma.pbo installed and no RKSL addon dependancies in the missions required addons, along with equalModRequired and verifySignatures disabled. If this does not fit in with your needs, you can always remove rksl-arma.pbo and access the RKSL addons in the traditional way, or failing everything else, contact us to see if we can help.

 

 



Add this page to your favorite Social Bookmarking websites
Digg! Reddit! Del.icio.us! Mixx! Free and Open Source Software News Google! Live! Facebook! StumbleUpon! TwitThis Joomla Free PHP
 

Add comment


Security code
Refresh

Who's Online

We have 27 guests online

Latest JComments

  • Quote:From what I’ve seen so far the new Arma 2 ex...
  • From what I’ve seen so far the new Arma 2 expiatio...
  • Hi Yeah, I was just enquiring about the medivac ve...
  • Im not entriely sure what you are asking for? Do ...
  • Looking good guys, as a regular (Arma 2) Puma pilo...