Talk:synchronizeObjectsAdd - Revision history

PierreMGI at 21:39, 29 February 2016

2016-02-29T21:39:49Z

← Older revision		Revision as of 23:39, 29 February 2016
Line 1:		Line 1:
	These synchronizeObjects add/remove commands work like links added/removed in editor SP or MP. But modules sometimes don't work as intended. For example, you can't cope with conditional codes, toggling these commands for enabling or not supports.		These synchronizeObjects add/remove commands work like links added/removed in editor SP or MP. But modules sometimes don't work as intended. For example, you can't cope with conditional codes, toggling these commands for enabling or not supports.
	If you link support modules and player(s), in initServerLocal.sqf for example, only player on hosted server will receive or loose these supports as intended. For remote players, modules can lead to disabled (grayed) support or, on contrary, repeated supports.		If you link support modules and player(s), in initServerLocal.sqf for example, only player on hosted server will receive or loose these supports as intended. For remote players, modules can lead to disabled (grayed) support or, on contrary, repeated supports.
	So, pay attention for MP behavior ~~enven~~ if stated as AG EG. The afterwards treatment can be weird (modules).		So, pay attention for MP behavior even if commands are stated as AG EG. The afterwards treatment can be weird (modules).

PierreMGI at 21:39, 29 February 2016

2016-02-29T21:39:04Z

← Older revision		Revision as of 23:39, 29 February 2016
Line 1:		Line 1:
	These synchronizeObjects add/remove commands work like links added/removed in editor SP or MP. But modules sometimes don't work as intended. For example, you can't cope with conditional codes, toggling these commands for enabling or not supports.		These synchronizeObjects add/remove commands work like links added/removed in editor SP or MP. But modules sometimes don't work as intended. For example, you can't cope with conditional codes, toggling these commands for enabling or not supports.
	If you link support modules and player(s), in initServerLocal.sqf for example, only player on hosted server will receive these supports as intended. For remote players, modules can lead to disabled (grayed) support or, on contrary, repeated supports.		If you link support modules and player(s), in initServerLocal.sqf for example, only player on hosted server will receive or loose these supports as intended. For remote players, modules can lead to disabled (grayed) support or, on contrary, repeated supports.
	So, pay attention for MP behavior enven if stated as AG EG. The afterwards treatment can be weird (modules).		So, pay attention for MP behavior enven if stated as AG EG. The afterwards treatment can be weird (modules).

PierreMGI at 21:37, 29 February 2016

2016-02-29T21:37:56Z

← Older revision		Revision as of 23:37, 29 February 2016
Line 1:		Line 1:
	These synchronizeObjects add/remove commands ~~works as~~ links in editor SP or MP. But modules sometimes don't work as intended. For example, you can't cope with conditional codes, toggling these commands for enabling or not supports.		These synchronizeObjects add/remove commands work like links added/removed in editor SP or MP. But modules sometimes don't work as intended. For example, you can't cope with conditional codes, toggling these commands for enabling or not supports.
	If you link support modules and player(s), in initServerLocal.sqf for example, only player on hosted server will receive these supports as intended. For remote players, modules can lead to disabled (grayed) support or, on contrary, repeated supports.		If you link support modules and player(s), in initServerLocal.sqf for example, only player on hosted server will receive these supports as intended. For remote players, modules can lead to disabled (grayed) support or, on contrary, repeated supports.
	So, pay attention for MP behavior enven if stated as AG EG. The afterwards treatment can be weird (modules).		So, pay attention for MP behavior enven if stated as AG EG. The afterwards treatment can be weird (modules).

PierreMGI: Created page with "These synchronizeObjects add/remove commands works as links in editor SP or MP. But modules sometimes don't work as intended. For example, you can't cope with conditional code..."

2016-02-29T21:36:47Z

Created page with "These synchronizeObjects add/remove commands works as links in editor SP or MP. But modules sometimes don't work as intended. For example, you can't cope with conditional code..."

New page

These synchronizeObjects add/remove commands works as links in editor SP or MP. But modules sometimes don't work as intended. For example, you can't cope with conditional codes, toggling these commands for enabling or not supports.
If you link support modules and player(s), in initServerLocal.sqf for example, only player on hosted server will receive these supports as intended. For remote players, modules can lead to disabled (grayed) support or, on contrary, repeated supports.
So, pay attention for MP behavior enven if stated as AG EG. The afterwards treatment can be weird (modules).