Scenario: Difference between revisions

From Tygron Preview Support Wiki
Jump to navigation Jump to search
← Older edit
Maxim@tygron.com (talk | contribs)
Tygron, Tygron_admin, Bureaucrats, Administrators
3,819 edits
No edit summary
 
(191 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{being updated}}
[[File:Api_multi_scenario.png|thumb|right|400px|[[Stakeholder]]s and [[Scenario]]s]]
{{learned|file=LevelsLogo-Q3-2015.jpg|what Levels are|how Levels relate to the Tygron engine|how to add Levels to your project|how to change Level properties in your project}}
By default, a project in the {{software}} always consists of at least one scenario.
==What are Levels?==
A Level is a relative position or rank on a scale.


==How do Levels relate to the Tygron Engine==
When you have multiple Scenarios, for example with two different designs for you project, you can switch between them from the ribbon bar in the editor. Currently, only one scenario can be active at the same time. Actions taken in a different scenario are reverted.
A project in the Tygron Engine can be set up as a Timeline based project. A session of such a project will progress along a time line, with the intention to see the impact of actions and measures on the indicators over time.


For different reasons it is possible to divide this timeline in two or more levels. Reasons to do so can be (but are not limited to) to provide the session participants a learning curve, to gradually make the project interaction more complex, to jump in time to a more distant future scenario, to provide pause moments in a session, etc.
==Limit Map==
Scenario's can be limited to a specific part of the map by selecting 'Measure Neighborhoods' in the Editor. This way only [[Neighborhoods]] that are covered by measures are active in the Scenario and the map is [[Limit Map|limited]] to these [[Neighborhoods]]. Using the margin attribute a margin can be added around the Neighborhoods.


By default, a project in the Tygron Engine always consists of at least one level.
==Attributes==
The attributes and description of an active Scenario are persistent (not reset) when stopping the testrun. This allows users to store attributes for later comparison between Scenario's.


==Adding, duplicating and removing Levels in a project==
{{article end
{{Editor ribbon|header=Storyline|bar=Levels|dropdown=Add new Level}}
|notes=
===Adding a Level===
* Scenarios are intended to become parallel planned situations
===Duplicating a Level===
|howtos=
===Removing a Level from a project===
* [[How to add or remove a Scenario]]
* [[How to change properties of a Scenario]]
* [[How to use a limit map in a Scenario]]
* [[How to change Events fired by a Scenario]]
* [[How to change Measures activated by a Scenario]]
* [[How to configure the available actions of a stakeholder per scenario]]
* [[How to configure an intro Cinematic for a Stakeholder and a Scenario]]
* [[How to use a limit map in a Scenario]]
}}


==Changing the properties of a level==
{{Editor multi scenario nav}}
{{Editor ribbon|header=Storyline|bar=Levels}}
[[Category:Items]]
 
===Level===
====Name====
====Description====
===Event Bundles===
====Server Events fired when chosen====
===Measures===
===Stakeholders===
====Provided Budget====
====Start with Cinematic====
====Active Action Menus====
===Playable Zones===

Latest revision as of 10:16, 13 November 2025

Stakeholders and Scenarios

By default, a project in the Tygron Platform always consists of at least one scenario.

When you have multiple Scenarios, for example with two different designs for you project, you can switch between them from the ribbon bar in the editor. Currently, only one scenario can be active at the same time. Actions taken in a different scenario are reverted.

Limit Map

Scenario's can be limited to a specific part of the map by selecting 'Measure Neighborhoods' in the Editor. This way only Neighborhoods that are covered by measures are active in the Scenario and the map is limited to these Neighborhoods. Using the margin attribute a margin can be added around the Neighborhoods.

Attributes

The attributes and description of an active Scenario are persistent (not reset) when stopping the testrun. This allows users to store attributes for later comparison between Scenario's.

Notes

  • Scenarios are intended to become parallel planned situations

How-to's

Multi Scenario
Multi Scenario
Stakeholders • Scenarios
Editor
Current Situation • Future Design • Multi Scenario • Tools • Community
Retrieved from "https://previewsupport.tygron.com/w/index.php?title=Scenario&oldid=63850"