View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001120EresseaGeneralpublic2007-02-04 12:112007-04-22 14:16
Reporterkhadar Assigned ToEnno  
PrioritynormalSeveritymajorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0001120: Damaged ship didn't sail although load was exactly at capacity
Description

One of my boats, damaged 5%, capacity 47.5, was loaded with exactly 47.5 GE. Despite that, I got the following error message:

Captain (r238) in Glades' Well (0,-2): 'MOVE w w' - The ship is too heavily loaded to sail.

This caused silver to not show up for upkeep of units landing on enemy shores this turn, making them unable to fight and easy prey for our opponents.

Additional Information

RTS Riptide (bq3c), boat, 5% Beschädigung Captain (r238) Guards (r296)

TagsNo tags attached.
Factionreg
Game
Report509

Activities

khadar

khadar

2007-02-04 12:19

reporter   ~0002501

This seems to be a problem with rounding/magellan. In the .nr the load/capacity is rounded at 48/47. In magellan it shows at 47.1/47.5...

Are shiploads and capacities always rounded?
Enno

Enno

2007-02-04 13:45

administrator   ~0002504

Eressea does not use fractions of weight. Anything weighing a fraction of a unit of weight (like silver) gets rounded up to the next full unit.
khadar

khadar

2007-02-04 14:00

reporter   ~0002505

I hate to disagree with you, but in this very same turn unit Captain (r217) carried 540 silver with a carrying capacity of 5.4... not a load of 6 GE with a capacity of 5... same works with units with carts and horses...

The rounding only happens with ships, then? Capacities are rounded down to the nearest whole number, and loads are rounded up?
Enno

Enno

2007-02-04 18:43

administrator   ~0002513

This is only done for ships, not units in general. I honestly don't remember why, and I think that you're right, it's confusing. So I've now changed the code to handle fractions of weight units for ships properly, and not try anything funny. Should be in effect from next week on.

Issue History

Date Modified Username Field Change
2007-02-04 12:11 khadar New Issue
2007-02-04 12:11 khadar Partei/Faction => reg
2007-02-04 12:11 khadar Report No. => 509
2007-02-04 12:19 khadar Note Added: 0002501
2007-02-04 13:45 Enno Status new => resolved
2007-02-04 13:45 Enno Resolution open => won't fix
2007-02-04 13:45 Enno Assigned To => Enno
2007-02-04 13:45 Enno Note Added: 0002504
2007-02-04 14:00 khadar Status resolved => feedback
2007-02-04 14:00 khadar Resolution won't fix => reopened
2007-02-04 14:00 khadar Note Added: 0002505
2007-02-04 18:43 Enno Status feedback => resolved
2007-02-04 18:43 Enno Resolution reopened => fixed
2007-02-04 18:43 Enno Note Added: 0002513
2007-04-22 14:16 Enno Status resolved => closed