Ryzom - View Single Post - Dialog and Storyline Design Guidelines Document

marct · September 20th, 2006, 11:10 PM

I agree, they need a name, and the name should be identical to there entity description unless there is more than 1. Then, it should number them or something. I have on several occasions had multiple of an entity and wanted them to act and be controlled seperately. Picking the right one in the events, actions, conditions, or dialog section is nearly impossible.

There must be some solution implemented for this.

EDIT: Nevermind, it seems I misinterpreted. This is that you wanted an ambiguous entity. I guess I would reference location, and then I might set a trigger or task that would identify that you did or did not reach the right one. Maybe have them turn about and ignore the person. The one that they were to talk to would have the context menu with a task, the others would not.

September 20th, 2006, 11:10 PM	#12
marct Join Date: Nov 2004 Location: If you need to, you know where to find me. Posts: 1,154	Re: Dialog and Storyline Design Guidelines Document I agree, they need a name, and the name should be identical to there entity description unless there is more than 1. Then, it should number them or something. I have on several occasions had multiple of an entity and wanted them to act and be controlled seperately. Picking the right one in the events, actions, conditions, or dialog section is nearly impossible. There must be some solution implemented for this. EDIT: Nevermind, it seems I misinterpreted. This is that you wanted an ambiguous entity. I guess I would reference location, and then I might set a trigger or task that would identify that you did or did not reach the right one. Maybe have them turn about and ignore the person. The one that they were to talk to would have the context menu with a task, the others would not.