[Trigger] Will local quest desync?

[Kazeon]

Hey fellas. Just like the title said, will creating a quest locally desync? As my PC broke and my laptop is unable to run multiplayer emulator so I can't test it myself. Thanks for any help.

 

[Wietlol]

Creating it will cause a desync, but showing it locally won't if done properly.

 

[Chaosy]

I would say it does not desync since it does only have a visual impact on the game.

I am not 100% certain since I have not tried, but that's usually how it works.

 

[Zwiebelchen]

Creating a local quest will desync, as Wietlol mentioned.

If you want quests "per player", you just create an array of quests (one for every player), then show them locally.

 

[Wietlol]

Showing them locally won't desync so you may still be able to use one quest that can be used by all players... right?

I have never used quests really so don't know 100%

 

[Zwiebelchen]

Showing them locally won't desync so you may still be able to use one quest that can be used by all players... right?

I have never used quests really so don't know 100%

Then you can not update the quest texts and requirements or flag them as completed.

 

[Ceday]

Wietlol is rigjt. You can use 1 quest for all players and mark it as completed or uncompleted locally or change text

Only tested this with Windows XP players

 

[Zwiebelchen]

Wietlol is rigjt. You can use 1 quest for all players and mark it as completed or uncompleted locally or change text

Only tested this with Windows XP players

You are asking for trouble when doing this. Since many natives can ask the quest state (and you might want to use these natives in triggers), a desync might result depending on what you do with the return value.
At some point in the game, you surely want to check if a quest is completed for a player or not and use that information for gameplay relevant stuff. Common example: spawning an NPC for a follow-up quest.

Tbh, it's not worth the trouble. I'd just create one quest copy for every player and always be one the secure side.