{{learned|what networks are|how networks relate to the Tygron Engine|how networks are structured|how to create networks}}
[[File:Api_current_situation_network.png|thumb|right|400px|Network with [[Net Node]]s connected by [[Net Line]]s, [[Net Load]]s clustered by [[Net Cluster]]s and configured by [[Net Setting]]s]]
{{stub}}
Networks in the platform are composed of multiple constituent components:
* [[Net Type]]: A categorization of the network.
* [[Net Node]]s: A node present in one or more networks
* [[Net Line]]s: A connection between two net nodes
** Has an associated [[Net Function]], which in turn is related to a specific [[net type]].
* [[Net Load]]s: A definition of supply or demand in the network
** Belongs to a particular [[Net Type]]
** Is associated to [[Net Node]].
** Can be activated or deactivated with specific time states.
* [[Net Cluster]]s: Cluster of net loads that provides group (de)activation.
** Can be associated with [[Net Load]]s of different [[Net Type]]s
* [[Net Setting]]s: Settings related to the configuration of a Network of a specific Net Type.
==What is a network==
A network is broadly defined as an interconnected system of things. More specifically, networks used here are transport and distribution networks. These are systems composed of interconnected points of supply and demand for specific resources, and the routes connecting them.
==How networks relate to the Tygron Engine==
In the Tygron Engine, it is possible to add network information to a project.
Network functionality is currently an advanced feature, and not available to new projects by default. Please contact Tygron Support if you wish to make use of networks in your projects.
===Restrictions on networks===
* Networks cannot contain any cycles. All networks should be defined as a tree. If the network is not structured as a tree, network generation and other calculations may have unexpected results.
* Net nodes may connect to one or more [[net line]]s, but [[net load|load nodes]] must connect to exactly one.
* Behavior is undefined if buildings linked to a network are altered during a session. Avoid demolishing, upgrading, selling, or changing these buildings when using network functionality.
{{article end
|howtos=
* [[How to generate a network using the network wizard]]
* [[How to import Net Lines using a GeoJSON]]
* [[How to import Net Loads using a GeoJSON]]
* [[How to manually edit a network]]
* [[How to check for errors when using the network wizard]]
* [[How to check for errors when using the net validation panel]]
|seealso=
* [[Network Overview Overlay]]
* [[Network Ownership Overlay]]
* [[Network Distance Overlay]]
|api=
* [[Api session items netnodes]]
* [[Api session event editor netline]]
* [[Api session event editor netload]]
* [[Api session event editor netcluster]]
* [[Api session event editor netsetting]]
|videos=
:[[File:Network_VT.jpg| link=https://youtu.be/k4WDyjdurU4|left|thumb|Network and network generation]]
Networks cannot contain any cycles. All networks should be defined as a tree. If the network is not structured as a tree, network generation and other calculations may have unexpected results.
Net nodes may connect to one or more net lines, but load nodes must connect to exactly one.
Behavior is undefined if buildings linked to a network are altered during a session. Avoid demolishing, upgrading, selling, or changing these buildings when using network functionality.
Current Situation