Eintragsdetails ansehen

IDProjektKategorieSichtbarkeitZuletzt aktualisiert
0003022EresseaSchiffeöffentlich2024-09-11 10:41
Reporterserpico Bearbeitung durchEnno  
PrioritätnormalSchweregradkleinerer FehlerReproduzierbarnicht getestet
Status geschlossenLösungkeine Änderung notwendig 
Produktversion29.1 
Zusammenfassung0003022: Leave and Attack
Beschreibung

Faction C transports Unit A Faction A in a boat(A), we land in a region. The region isn't guarded and is empty. The same week, another boat(B) has landed with Unit B Faction B. The Unit A leaves the boat A and attack the Unit B. Unit B is the captain of the boat B, so he has surely not leaved the boat. Faction C isn't involved in the combat.

Combat duration 5 rounds => Unit B doesn't flee

After the battle : Boat B of Unit B : no damage, and UNIT B still inside Boat B that has transported Unit A : 20% damage And at the end of the week Unit A is outside the boat A ( so that means the order of leave has been given)

In sequence LEAVE is before ATTACK Is that a bug ?

TagsKeine Tags zugeordnet.
Parteiara
SpielE2
Report1350

Notizen / Dateien

Solthar

Solthar

2024-04-10 11:54

Entwickler   ~0010156

Did unit a hit, in other words, is there a line like "a (a) hit 2 times and killed 0 enemies." in the report? Otherwise this probably worked as intended and there is just a bug in the rules: Units that left a ship in the same round still cause damage to the ship if they are hit.

Solthar

Solthar

2024-04-10 13:52

Entwickler   ~0010159

Include the report in ``` to keep the formatting. So Cemmentarius hit, but Kleinohr's boat was not damaged? Then there is something I do not understand. Is it possible, that the hit caused 0 damage somehow? An unarmed troll should do d5+1 damage and I can reproduce the case when B has no armor. What's the modifier for skill difference in this case?

Enno

Enno

2024-04-10 21:52

Administrator   ~0010161

LEAVE is before ATTACK, but (and this is missing in the documentation) to make Invasions from sea more difficult, if any unit that is on a ship at the end of the previous turn (i.e. in the last report) takes damage in combat, then the ship that it's either still on or that it has just left will also take damage.

Solthar

Solthar

2024-04-11 10:09

Entwickler   ~0010163

Zuletzt bearbeitet: 2024-04-11 10:14

I think I've got it. There is a rule implemented that ships only take damage in "long" battles (therefor the max. damage is 20%, not 25% or 30%). "Die Taktikrunde und die erste Runde wird nicht mitgezählt, so dass es immer nur maximal 20% Schaden geben kann." This is implemented in 3 places:
https://github.com/eressea/server/blob/96bbeef40077a35a1af8334131ac58600e3f0953/src/battle.c#L959
https://github.com/eressea/server/blob/96bbeef40077a35a1af8334131ac58600e3f0953/src/battle.c#L2600
https://github.com/eressea/server/blob/96bbeef40077a35a1af8334131ac58600e3f0953/src/battle.c#L2802
The effect is, that the ship did not take damage because it was only hit in turn 1 (of 5).

Maybe the first line (turn>1) is actually not reflecting the rule as intended: It shouldn't really matter if the hit was in round 1 or 2, only if the battle went to round 2. I think that from a world perspective, that makes more sense. On the other hand, there could be a situation, where a fight lasts 5 rounds, but not actually for the unit on the ship: The unit might have fled or their opponents might be dead already by round 2. Should the ship really take damage because there was fighting going on somewhere else in the region? But we should discuss this here: https://discord.com/channels/509396702663278592/981092975088140348/1227893196282003516

Enno

Enno

2024-05-29 21:45

Administrator   ~0010196

Is there still a bug report here? Or is this just a rules discussion? Can the ticket be closed?

serpico

serpico

2024-05-30 08:14

Reporter   ~0010197

can be closed. wiki have to be updated to allow how things work

Eintrags-Historie

Änderungsdatum Benutzername Feld Änderung
2024-04-09 14:50 serpico Neuer Eintrag
2024-04-09 16:37 Xolgrim Beschreibung aktualisiert
2024-04-09 19:32 Xolgrim Schweregrad Absturz => kleinerer Fehler
2024-04-09 19:32 Xolgrim Produktversion 3.3 => 29.1
2024-04-10 11:54 Solthar Notiz hinzugefügt: 0010156
2024-04-10 13:52 Solthar Notiz hinzugefügt: 0010159
2024-04-10 21:52 Enno Notiz hinzugefügt: 0010161
2024-04-11 10:09 Solthar Notiz hinzugefügt: 0010163
2024-04-11 10:14 Solthar Notiz bearbeitet: 0010163
2024-05-29 21:45 Enno Notiz hinzugefügt: 0010196
2024-05-30 08:14 serpico Notiz hinzugefügt: 0010197
2024-09-11 10:41 Enno Bearbeitung durch => Enno
2024-09-11 10:41 Enno Status neu => geschlossen
2024-09-11 10:41 Enno Lösung offen => keine Änderung notwendig