Difference between revisions of "Ulite: Territories"
(created page with translated text. tables need work.) |
m (→3.13.4.2 Station attacks) |
||
Line 48: | Line 48: | ||
====3.13.4.2 Station attacks==== | ====3.13.4.2 Station attacks==== | ||
− | + | Station attacks are always permitted. | |
The attacked alliance (or station owners) will receive a message when enemy fleets reach scanner range. | The attacked alliance (or station owners) will receive a message when enemy fleets reach scanner range. | ||
Time blocking for station attacks is 1 day. | Time blocking for station attacks is 1 day. |
Latest revision as of 11:21, 2 January 2017
Contents
3.13 Territories
3.13.1 Basic principles
Any number of sectors can be assigned to an alliance. These sectors then call themselves territory. For an alliance to have a sector assigned, it must meet certain conditions. An alliance then has special rights in its own territory regarding station building and attacks.
3.13.2 Assignment rules
All sectors in the core area (that is block [-10, -10] to [+ 10, + 10]) are neutral. All external sectors are neutral if they are not assigned to an alliance. An alliance must have "3" (or 3 more than another) systems "owned" to get the sector awarded. "Owned" means that the system must have at least one territorial station of the alliance and no territorial station of another alliance. Between the territories of two alliances, at least one sector must be "neutral". The territory of an alliance must be contiguous. In the case of several possible territories, the largest one is selected, then the oldest one.
3.13.3 Visible Territory
The territories and systems "owned" are publicly known. There is also a global message of DTR in sector allocations. Once an alliance has a system in a sector, or a system more than another alliance, then the also universe.php visible.
3.13.3.1 Universe Map
Link: Universe Map
When an alliance receives a sector, the corresponding sector is marked with the corresponding alliance color in this view. These sectors (squares) are thus completely filled with the alliance color.
Already, if an alliance has a system "owned", this can be seen by the "framework" of the sector. The frame strength (in pixels) indicates the number of occupied systems that this alliance has more than others.
3.13.3.2 Local Map
Link: Local Map
Systems that are "owned" by an alliance are drawn in their alliance color. Published systems are white. Published systems that belong to an alliance territory have a white name, but the position line is in the Alliance color.
3.13.3.3 System list
Link: Ship Systems OR Systems.
The sector number and the system name are shown in the Alliance color if the sector is Alliance territory. In addition, the abbreviation of the alliance appears.
3.13.4 Effects
3.13.4.1 Ship attacks
In an inhabited system in the core area is generally no firing allowed (penalty points). In their own territory, ships are always attacked (no penalty points).
3.13.4.2 Station attacks
Station attacks are always permitted. The attacked alliance (or station owners) will receive a message when enemy fleets reach scanner range. Time blocking for station attacks is 1 day.
3.13.4.3. Docking permits at stations
The docking at Private Stations is "neutral" for the alliance relationships (which is also given if a player does not belong to any alliance) and above (NAP, Alliance). No docking is possible for others.
3.13.4.4. Reasons for stations
In sectors that are assigned to an alliance, only these alliance stations may be created.
3.13.5 Publishing stations
3.13.5.1 Basic principles
The goal is for Alliances to claim as many sectors as possible. These are counted and in the high score lists. Each player has only a limited number of stations (Station Admin skill). In order for the territory to be enlarged, the player must publish his stations. This means that the station will go completely into the public hand, but it will still be considered for the alliance territory.
3.13.5.2. Publishing Conditions
The station must have 7 buildings and 2000 points.
3.13.5.3. Publishing Station Effects
The station becomes public, and no longer belongs to the founder. The founder can no longer use resources (shipbuilding, research) of the station. Other orbital stations are randomly generated. All stored goods remain there, but the values are reimbursed to the Alliance in cash.