Client Side RPT Errors

[Anthrax]

Trying to debug some client side stuff. Any help is always appreciated. I have a copy of this client rpt just not sure how to post it. Everything works ok but errors are not acceptable. There is another 1000+ lines of warning on the client side also but I assume they are common and don't matter. Here is the client side rpt stuff im concerned the most of at the moment. :)

Error in expression < getVariable["actionSet", false];

if (!_actionSet) then {
s_player_holderPickup>
  Error position: <_actionSet) then {
s_player_holderPickup>
  Error Undefined variable in expression: _actionset
File z\addons\dayz_code\init\object_BackpackAction.sqf, line 13

Error in expression <= -1;
};
} else {
_vehicle removeAction s_player_nitrobooston;
s_player_nitroboo>
  Error position: <s_player_nitrobooston;
s_player_nitroboo>
  Error Undefined variable in expression: s_player_nitrobooston
File mpmissions\__CUR_MP.Napf\custom\fn_selfActions.sqf, line 34

Error in expression <"",""];
};
} else {
player removeAction s_player_nitroInstall;
s_player_nitroIns>
  Error position: <s_player_nitroInstall;
s_player_nitroIns>
  Error Undefined variable in expression: s_player_nitroinstall
File mpmissions\__CUR_MP.Napf\custom\fn_selfActions.sqf, line 823

[Anthrax]

From what I understand the s_player_holderPickup> cannot be fixed OK cool.

I sure would like to get this nitro error off my players side. Ya I know I should be able to figure it out... Well 40 years puts a toll on ya ;) So help a guy out please....

[Buck0]

Variables.sqf

dayz_resetSelfactions ={

s_player_nitroinstall = -1;

Ect for each undefined error your getting

[Anthrax]

Might be getting closer but still no cigar. Thanks Buck0. I'll get r figured out soon. Can't believe I haven't fingered it out yet... same exact nitro errors.

[Anthrax]

Thinking I need to add 'some part of this nitro script' in the custom compiles and possibly move the variables to custom also? 

[axeman]

Error in expression is normally a syntax mistake. Look up the command on the BIS Wiki.

Undefined variables, well just define them, always ! Is good practice and lately Arma has started to insist on it.

At the top of your code, or at a point in the code where you know it is the first time the engine queries that variable, define it. Even if it is just _myObjectIWillUseLater = objNull; at the start. FSM pissess and moans all the time about this.

Also, sometime the errors aren't where the log says they are, a missing semi colon can throw a weird error several lines later, always trace back up your code if the error doesn't make sense.

Then, there are the typos, the ones that you just can't see cos you been staring at the code for too long :)

In your 'if actionset', I always put the not ! outside of the brackets. If !(_boolVar) then... A habit formed over time.

[Anthrax]

Thank you axeman.