Page MenuHomeFeedback Tracker

Server public variables not available in client preInit
Closed, ResolvedPublic


Broadcasted server public variables are not available in client preInit.

That's a major issue as it also affects paramsArray which is also not available on clients in preInit.

Debug output looks like this in client RPT:

[33567,893.745,0,"Executing fn_preinit.sqf"]
["preInit value of client pvtestvar:",any]
["preInit value of client paramsArray:",any]
[33567,893.77,0,"fn_preinit.sqf processed"]
[35964,897.012,0,"Executing init.sqf"]
["init.sqf value of client pvtestvar:",1]
["init.sqf value of client paramsArray:",[1]]
[35964,897.012,0,"init.sqf processed"] {F22637}


Legacy ID
No Bug
Steps To Reproduce

Start the attached mission on a dedicated server (it will send one test public variable from the server and has class params in description.ext).

After the mission has started check client RPT. Both, the server test public variable and paramsArray are nil in preInit.

Event Timeline

Xeno edited Steps To Reproduce. (Show Details)Oct 28 2013, 6:44 AM
Xeno edited Additional Information. (Show Details)
Xeno set Category to Scripting.
Xeno set Reproducibility to Always.
Xeno set Severity to None.
Xeno set Resolution to No Bug.
Xeno set Legacy ID to 2974581187.May 7 2016, 5:15 PM
Xeno added a subscriber: Xeno.
Xeno added a comment.Oct 28 2013, 12:48 PM

It makes sense to downvote a bug in the preInit implementation...

This is intentional. That's why it's called "preInit" - because it's executed before anything else is initialized. I recommend to use "postInit" instead.

Xeno added a comment.Nov 13 2013, 8:49 AM

Well, it affects paramsArray too (which seems to be nothing more than a PV too).

Sad to see that this will also not change.

Mass closing resolved issues not updated since November.

Xeno removed a subscriber: Xeno.May 29 2016, 11:49 PM