This Trac instance is not used for development anymore!

We migrated our development workflow to git and Gitea.
To test the future redirection, replace trac by ariadne in the page URL.

Opened 16 years ago

Last modified 14 years ago

#221 closed defect

Resource counters went negative — at Version 1

Reported by: Jan Wassenberg Owned by:
Priority: Nice to Have Milestone:
Component: Core engine Keywords:
Cc: Anton Galitch, dacian Patch:

Description (last modified by Michael D. Hafer)

In an 1v1 game of Oasis, the stone resource counter was observed to be -1. After starting at 100 and building two houses (50 stone each), it should have been zero (and probably was). After a while of further play - without any harvesting of stone - the resource counter was shown as "-1". Failed to duplicate this in SP, so it's probably related to network transmission of the value.

Change History (1)

in reply to:  description comment:1 by Michael D. Hafer, 16 years ago

Description: modified (diff)

Replying to jan:

In an 1v1 game of Oasis, the stone resource counter was observed to be -1. After starting at 100 and building two houses (50 stone each), it should have been zero (and probably was). After a while of further play - without any harvesting of stone - the resource counter was shown as "-1". Failed to duplicate this in SP, so it's probably related to network transmission of the value.

Unverified: Could also possibly have to do with the "looting" feature. If one of your units was killed, it is possible the "loot" from his death was taking from your stockpile. I believe by default (in one of the parent files), "loot" is set at 1 for each resource. But of course your idea about network transmission might be correct.

This will take some verification (testing).

Note: See TracTickets for help on using tickets.