Author Topic: Is issue #269 related to issue #263?  (Read 1800 times)

0 Members and 1 Guest are viewing this topic.

Offline Forestidia86

  • Posts: 731
  • inactive
    • View Profile
Is issue #269 related to issue #263?
« on: December 03, 2017, 06:16:52 AM »
I ask only out of curiosity; I'm no programmer and have no knowledge of D as language, so sorry if this question is out of place.

Issue #263 has as main error message:
core.exception.AssertError@src/game/tribe.d(210): Assertion failure

and issue #269 has:
core.exception.AssertError@src/game/tribe.d(211): Assertion failure

The numbers are different and one is reported to have happened at the beginning and the other at the end of a multiplayer game but there seem quite some similiarities apart from that both happened to geoo.

One side remark: It seems that Lix error windows appear in the background (at least for Windows XP, 7). That seems to make them (or even a crash) hard to spot. I don't know if there is something to do about it.
« Last Edit: December 03, 2017, 06:53:12 AM by Forestidia86 »

Offline Simon

  • Administrator
  • Posts: 3954
    • View Profile
    • Lix
Re: Is issue #269 related to issue #263?
« Reply #1 on: December 03, 2017, 09:51:18 PM »
Thanks for linking these two. I agree that it's likely the same bug merely hitting at two different times.

When somebody nukes, then scores, the game believed, wrongly, that the overtime has been running since their nuke, when, correctly, the overtime should run since their save. geoo plays networked games with a debugging build, and it fails an assert in a contract. The contract is correct, there is a real bug here.

Should be fixed in next release!

-- Simon