From Tygron Preview Support Wiki
Jump to navigation Jump to search


An action is an activity a stakeholder can perform to potentially achieve their objectives. A typical example of an action would be a housing corporation constructing social housing, or a water board realizing open water.

When a user plans an action, it changes the future situation and will often have an effect on overlays and indicators. For example, when a stakeholder plants new trees, this action will have an effect on the Livability overlay and consequently on the Livability indicator.

Actions taken are tied to specific stakeholders, allowing the recording of costs and incomes. As an example, the waterboard can be configured to have the capability to create waterways, but not social housing or roads. Since a stakeholder can be configured to have access to many different actions available, actions are organized using Action menus.

Planned actions are generally not final. They can be canceled by the stakeholder that performed the action and sometimes be reverted by stakeholders that own the property. For reverting actions, see #Special Actions

Each action is logged in the Action Log, which can be used to trace back which actions have been taken during a session or test run.

Predefined Actions

A lot of predefined actions are available in Tygron Platform. Each project can have its own set of available actions. Furthermore, not every action has to be available for each stakeholder. Since Projects created in the Tygron Platform have their focus primarily on urban planning, most of the available actions are construction options. These options allow stakeholders to plan constructions based on available functions.

For more information about all the actions available in the Tygron Platform, see the list of actions.

Types of Actions

This section describes the types of actions that can be taken and what effect they will have when planned in your project.

Actions that require a drawn selection:

The most common type of action, the function, can be applied to your project by drawing a selection. When applied, a building with that function will be planned in your project.
Buildings can be upgraded using Upgrade Types, provided an upgrade definition exists within that Upgrade Type which applies to that building's function. Upgrades can be used to improve the building to a related function, or to change the building to a completely different function category.
Similar to upgrades, although these actions do not change the function of a building. Instead, they set particular attribute values. These values can be set (at locked) by the creator of the action, or be configured by stakeholders applying these actions.
These are actions that have a functionality that cannot be further configured. These actions are grouped together as Special actions.

Actions that open an additional panel:

Actions that will be applied directly:

Impact of Actions

Most actions have effects on buildings; planning new or demolishing or upgrading them. This will often have an effect on one or more indicators. Each action on a building has a cost that will negatively affect the acting stakeholder's budget.

For changing the effects of the buildings on the indicators, see functions.

Measures and Events

Measures and events also need to be defined before they can be added to a stakeholder's action menu. Events simply cause other things to happen during the session when they are activated. Measures may have a variety of effects.

Action Menus

For each stakeholder, their actions are organized into menus. Similar actions, such as creation of infrastructure (roads, traintracks, etc) or housing (villas, apartments, etc), can be grouped together into the same menu. By roughly matching the actions in a menu to the indicators relevant to the stakeholder, it is possible for users to weigh choices of actions against each other easily.

Action menus can also be shared between stakeholders. This means that two or more stakeholders can have access to the same menu, and to the same actions within that menu. An example of a menu that could be shared among stakeholders would be a menu with financial actions, such as the ability to transfer money. Having a menu shared with another stakeholder has no effect on the usability of a menu or the actions therein.