Befehlsreihenfolge/en: Unterschied zwischen den Versionen

Aus Eressea
Zur Navigation springenZur Suche springen
Keine Bearbeitungszusammenfassung
(Die Seite wurde neu angelegt: „Orders of the same rank from different units are normally processed in the order 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. itempool also usually works in this order. However, this can be changed by certain commands. These include ENTER, LEAVE, MAKE TEMP, GIVE CONT…“)
Zeile 71: Zeile 71:
== Which unit acts first ==
== Which unit acts first ==


<div lang="de" dir="ltr" class="mw-content-ltr">
Orders of the same rank from different units are normally processed in the order 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. [[Special:MyLanguage/Materialpool|itempool]] also usually works in this order. However, this can be changed by certain commands. These include ENTER, LEAVE, MAKE TEMP, GIVE CONTROL and GIVE SHIP. The exact behaviour is not guaranteed! Therefore, if in doubt, give orders in such a way that the unit order does not matter.
Gleichrangige Befehle verschiedener Einheiten werden normalerweise in der Reihenfolge abgearbeitet, wie sie im Report erscheinen. Also zum Beispiel erst alle GIB-Befehle der ersten Einheit, dann alle GIB-Befehle der zweiten Einheit, später alle REKRUTIERE-Befehle der ersten Einheit, dann der zweiten und so fort. Auch der [[Special:MyLanguage/Materialpool|Materialpool]] funktioniert üblicherweise in dieser Reihenfolge. Das kann sich jedoch durch bestimmte Befehle verändern. Dazu gehören BETRETE, VERLASSE, MACHE TEMP, GIB KOMMANDO und GIB SCHIFF. Das genaue Verhalten wird nicht garantiert! Deshalb sollte man im Zweifel Befehle so geben, dass die Einheitenreihenfolge dafür keine Rolle spielt.
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
<span id="Siehe_auch"></span>
== Siehe auch ==
== See also ==
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
<div lang="de" dir="ltr" class="mw-content-ltr">

Version vom 5. März 2024, 13:14 Uhr

Sprachen:

Eressea's orders are evaluated in a fixed sequence. Orders with the same number are executed at the same time.

The point of this is that all factions are "served" equally and not the unit that is first in line gets all the resources.

  1. new default orders are set
  2. GROUP, MAKE TEMP
  3. NAME, DESCRIBE, GUARD NOT, HELP, COMBAT, COMBATSPELL, HIDE, ORIGIN, SHOW
  4. BANNER, EMAIL, OPTION, PASSWORD
  5. CONTACT
  6. MESSAGE
  7. ENTER ; 1. attemp
  8. USE
  9. LEAVE
  10. ENTER; 2. attemp
  11. ATTACK
  12. RESERVE, CLAIM
  13. ENTER; 3. attemp
  14. GIVE CONTROL
  15. FORGET
  16. GIVE
  17. RECRUIT is first remembered, then executed person by person
  18. DESTROY
  19. FOLLOW is set
  20. PROMOTE
  21. PAY NOT Sets function and maintenance costs for the corresponding building.
  22. Maintenance costs for buildings are accounted for. If they cannot be raised, the building has no effect for that turn!
  23. QUIT
  24. CAST
  25. TEACH
  26. LEARN
  27. MAKE
  28. RESEARCH, PLANT, SPY, GROW
  29. ENTERTAIN
  30. TAX
  31. WORK
  32. BUY
  33. SELL
  34. STEAL
  35. Ships with not enough crew suffer damage.
  36. ENTER 4. attemp
  37. MOVE and ROUTE, including RIDE and CARRY are executed, and units order to FOLLOW other units do so.
  38. GUARD this only works if the unit has not moved.
  39. Ships drifting on the high seas
  40. DEFAULT
  41. Empty units are removed
  42. Peasants, horses and trees grow if possible; the remaining peasants move into other regions.
  43. Silver for units maintenance is subtracted
  44. SORT
  45. NUMBER

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 fights, receives 300 silver, recruits 1, and finally learns FORESTRY - although this is not the sequence in which the commands were written.

Explanations

About ENTER
1st/2nd/3rd/4th Attempt:
This means that you can still enter a castle before an attack. 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 accordingly. If you completely kill or drive out a building crew in combat, you can enter the castle after the fight.

Which unit acts first

Orders of the same rank from different units are normally processed in the order 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. itempool also usually works in this order. However, this can be changed by certain commands. These include ENTER, LEAVE, MAKE TEMP, GIVE CONTROL and GIVE SHIP. The exact behaviour is not guaranteed! Therefore, if in doubt, give orders in such a way that the unit order does not matter.

See also


Continue reading: Kurzbeschreibung