Befehlsreihenfolge/en: Unterschied zwischen den Versionen
(Übernehme Bearbeitung einer neuen Version der Quellseite) |
Keine Bearbeitungszusammenfassung |
||
(7 dazwischenliegende Versionen von 2 Benutzern werden nicht angezeigt) | |||
Zeile 11: | Zeile 11: | ||
# [[Special:MyLanguage/BENUTZE|USE]] | # [[Special:MyLanguage/BENUTZE|USE]] | ||
# [[Special:MyLanguage/VERLASSE|LEAVE]] | # [[Special:MyLanguage/VERLASSE|LEAVE]] | ||
# [[Special:MyLanguage/BETRETE|ENTER]]; | # [[Special:MyLanguage/BETRETE|ENTER]]; 2nd attempt | ||
# [[Special:MyLanguage/ATTACKIERE|ATTACK]] | # [[Special:MyLanguage/ATTACKIERE|ATTACK]] | ||
# [[Special:MyLanguage/RESERVIERE|RESERVE]], [[Special:MyLanguage/BEANSPRUCHE|CLAIM]] | # [[Special:MyLanguage/RESERVIERE|RESERVE]], [[Special:MyLanguage/BEANSPRUCHE|CLAIM]] | ||
Zeile 59: | Zeile 59: | ||
END | END | ||
Here the | Here the orders sequence is: | ||
The new unit is first created, no longer joins combats, receives 300 silver, recruits 1, and finally learns forestry - although this is not the sequence in which the orders were written. | The new unit is first created, no longer joins combats, receives 300 silver, recruits 1, and finally learns forestry - although this is not the sequence in which the orders were written. | ||
Zeile 65: | Zeile 65: | ||
== Notes == | == Notes == | ||
Orders of the same rank from different units are normally processed in the sequence in which they appear in the report. For example, first all GIVE orders of the first unit, then all GIVE orders of the second unit, then all RECRUIT orders of the first unit, then the second and so on. The[[Special:MyLanguage/Materialpool|item pool]] also usually works in this way: units higher up in the region are first "asked" if the can share a certain item. However, this sequence can be changed by certain commands. These include ENTER, LEAVE, MAKE TEMP, GIVE CONTROL and GIVE SHIP. The exact behavior is not guaranteed! Therefore, if in doubt, give orders in such a way that the unit sequence does not matter. | Orders of the same rank from different units are normally processed in the sequence in which they appear in the report. For example, first all GIVE orders of the first unit, then all GIVE orders of the second unit, then all RECRUIT orders of the first unit, then the second and so on. The [[Special:MyLanguage/Materialpool|item pool]] also usually works in this way: units higher up in the region are first "asked" if the can share a certain item. However, this sequence can be changed by certain commands. These include <tt>ENTER, LEAVE, MAKE TEMP, GIVE CONTROL</tt> and <tt>GIVE SHIP</tt>. The exact behavior is not guaranteed! Therefore, if in doubt, give orders in such a way that the unit sequence does not matter. | ||
For orders where the result has an upper limit, for example the maximum number of trees in the region for <tt>MAKE wood</tt>, the maximum number of recruits to <tt>RECRUIT</tt> or the region's money for <tt>ENTERTAIN</tt> and <tt>TAX</tt>, it may happen that several units are in competition. In this case, we try to distribute the scarce good in proportion to the quantity that each unit could produce if it were unlimited. In this case, there may be gaps and a unit may end up with nothing. The <tt>SELL</tt>, <tt>BUY</tt> and <tt>WORK</tt> orders are also affected. | |||
; About ENTER 1st/2nd/3rd/4th attempt: | ; About ENTER 1st/2nd/3rd/4th attempt: |
Aktuelle Version vom 8. März 2024, 13:00 Uhr
Eressea's orders are evaluated in a fixed sequence. Orders with the same number are executed at the same time or the exact sequence is irrelevant.
- new default orders are set
- GROUP, MAKE TEMP
- NAME, DESCRIBE, GUARD NOT, HELP, COMBAT, COMBATSPELL, HIDE, ORIGIN, SHOW
- BANNER, EMAIL, OPTION, PASSWORD
- CONTACT
- MESSAGE
- ENTER; 1st attempt
- USE
- LEAVE
- ENTER; 2nd attempt
- ATTACK
- RESERVE, CLAIM
- ENTER; 3rd attempt
- GIVE CONTROL
- FORGET
- GIVE
- RECRUIT*
- DESTROY
- FOLLOW is set
- PROMOTE
- PAY NOT; stops operation and maintenance costs for the corresponding building.
- maintenance costs for buildings are accounted for. If they cannot be raised, the building has no effect for that turn!
- QUIT
- CAST
- TEACH
- LEARN
- MAKE *
- RESEARCH, PLANT, SPY, GROW
- ENTERTAIN *
- WORK *
- TAX *
- BUY *
- SELL *
- STEAL *
- ships with insufficient crew suffer damage
- ENTER; 4th attempt
- MOVE and ROUTE, including RIDE and CARRY are executed, and units ordered to FOLLOW other units do so
- GUARD; this only works if the unit has not moved.
- ships drift on the high seas
- DEFAULT
- empty units are removed
- peasants, horses and trees grow, if possible; the remaining peasants move into other regions
- silver for units maintenance is subtracted
- SORT
- NUMBER
* Orders marked like this are divided "fairly"; see notes below.
However, the orders do not necessarily have to be entered in this order. It is perfectly permissible to enter the following:
GIVE TEMP 5 300 Silver MAKE TEMP 5 RECRUIT 1 COMBAT NOT LEARN FORESTRY END
Here the orders sequence is: The new unit is first created, no longer joins combats, receives 300 silver, recruits 1, and finally learns forestry - although this is not the sequence in which the orders were written.
Notes
Orders of the same rank from different units are normally processed in the sequence in which they appear in the report. For example, first all GIVE orders of the first unit, then all GIVE orders of the second unit, then all RECRUIT orders of the first unit, then the second and so on. The item pool also usually works in this way: units higher up in the region are first "asked" if the can share a certain item. However, this sequence can be changed by certain commands. These include ENTER, LEAVE, MAKE TEMP, GIVE CONTROL and GIVE SHIP. The exact behavior is not guaranteed! Therefore, if in doubt, give orders in such a way that the unit sequence does not matter.
For orders where the result has an upper limit, for example the maximum number of trees in the region for MAKE wood, the maximum number of recruits to RECRUIT or the region's money for ENTERTAIN and TAX, it may happen that several units are in competition. In this case, we try to distribute the scarce good in proportion to the quantity that each unit could produce if it were unlimited. In this case, there may be gaps and a unit may end up with nothing. The SELL, BUY and WORK orders are also affected.
- About ENTER 1st/2nd/3rd/4th attempt
- This means that you can still enter a castle before an attack. After the fight, a unit may try to enter again, as the former owner might be dead or has fled in the meantime.
- It does not mean that units leaving a ship can still attack in the same turn, as the server remembers who left ships and intercepts it accordingly.
See also
Continue reading: | Short Description |