Repairing (physically/visually)

[Loyalguard]

If you change your init.sqs to init.sqf it would/should look like this:

// Initialize revive script
server execVM "revive_init.sqf";

_nul = [] execVM "repair.sqf";

[Ironman]

what is the _nul for?

[Loyalguard]

_nul is what is called a "handle" and is used with the execVM or spawn commands.  It's a way of identifying a script and/or storing any return values (the latter being one of the most common uses).  It can be in the form of a global or local variable.  In the example I gave you, I designated it _nul to mark it as something from which I don't expect any return value.  You can call it anything as long as you follow the normal variable rules.  A good example of where a return might be useful using execVM is the addAction command where the handle stores the unique ID of of the action.

[Ironman]

Ok, so the "_nul" will handle and returns that might be sent back. In this case, none will be sent.

So it is like Java's:

public void blahBlah()
{

}

where void is the return type.... right?

[Loyalguard]

Whether there is a return or not depends on the code that follows the handle I think.  Using "_nul" doesn't actually destroy or block the return, it is more to informally remind you that you are ignoring this return as you have no use for it.  I could have written "_ignoreThis" or "_noReturn" or anything for the same purpose. I use "_nul" because it is a quick easy fit.  Sorry for any confusion.

[Rommel92]

Ok, so the "_nul" will handle and returns that might be sent back. In this case, none will be sent.

So it is like Java's:

public void blahBlah()
{

}

where void is the return type.... right?

Code: (add.sqf) [Select]

private ["_a","_b","_c"];
_a = _this select 0;
_b = _this select 1;
_c = _a + _b;
_c

_m = [1,2] execVM "add.sqf";
_m == 3;

Hope that helps, the fact that he put _nul there has nothing to do with the word, it just means... Null, nothing, if you wished to use the return value, you could still use _nul, but most times you wouldn't for easy reading/debugging.

Variable = Return of Operation.
So if:
"_VAR = 1 + 15" then _VAR = 16, not 1 + 15. And if you do variables inside this, "_VAR = _vA + _vB" then _VAR = whatever _vA and _vB equal at that time, say their both 10, _VAR = 20. If _vA or _vB change to say 2, _VAR will still = 20 unless you do the _VAR = _vA + _vB operation again (which would mean _VAR = 4), as it does not store the variables, it stores the RESULT, or the Return of the Operation.

I think I went a bit off topic...