search

vassalengine / vassal

VASSAL, the open-source boardgame engine
https://vassalengine.org
GNU Lesser General Public License v2.1
430 stars 103 forks source link

[1960] Save game function returns map to starting influence cubes #12570

Open Twinridge opened 1 year ago

Twinridge commented 1 year ago

Twice now, when both of us were playing under 3.6.17, we tried to save a game. It preserved almost of the aspects of the game: cards in the discard pile, cards in the event holding boxes, endorsements and media cubes were all correct, but it wipes out all the influence cubes accumulated during the game and reverts to the starting position (in terms of cubes on the map) for both players. The player cylinders remain in their last position.

uckelman commented 1 year ago

The current version is 3.6.19. Can you reproduce the problem with that?

Twinridge commented 1 year ago

Joel,  I haven't tried it with 3.6.19, in part because the info page for the 1960 module only claims it is compatible with 3.6.17. Richard Comfort & Kathy Bowers 434-978-2980 

On Monday, August 14, 2023, 05:32:57 PM EDT, Joel Uckelman ***@***.***> wrote:

The current version is 3.6.19. Can you reproduce the problem with that?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

uckelman commented 1 year ago

The compatibility listings for modules are typically minima. (It's a thing we have plans to clarify.) Please try with 3.6.19.

Twinridge commented 1 year ago

Yes, still doing it with 3.6.19.  It preserves cubes placed on the Issues and Rest cubes, cards in the various Discard/Out-of-Play piles, but it still reverts to the starting cube placement on the map. Richard Comfort & Kathy Bowers 434-978-2980 

On Monday, August 14, 2023, 05:49:30 PM EDT, Joel Uckelman ***@***.***> wrote:

The compatibility listings for modules are typically minima. Please try with 3.6.19.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

uckelman commented 1 year ago

I was able to reproduce the problem. Have you contacted the module's maintainer about it?

Twinridge commented 1 year ago

No, this is the first time I've reported a bug.   I just followed the instructions - though they need to be updated, since they make no mention of github. Richard Comfort & Kathy Bowers 434-978-2980 

On Monday, August 14, 2023, 07:16:53 PM EDT, Joel Uckelman ***@***.***> wrote:

I was able to reproduce the problem. Have you contacted the module's maintainer about it?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

uckelman commented 1 year ago

I suggest contacting the maintainer of the module about this problem, as it might be a module bug. You can find the contact details of the module's maintainer if you visit the module's page and are logged in.

What bug reporting instructions are you referring to? Please provide a URL.

Twinridge commented 1 year ago

Ok, thanks, I'll contact Joel. Here's the page I came to when looking for how to report a bug...the hotlink says vassalengine.org/tracker, but takes one to github (where I had to create an account to proceed).

Richard Comfort & Kathy Bowers 434-978-2980 

On Monday, August 14, 2023, 07:57:11 PM EDT, Joel Uckelman ***@***.***> wrote:

I suggest contacting the maintainer of the module about this problem, as it might be a module bug. You can find the contact details of the module's maintainer if you visit the module's page and are logged in.

What bug reporting instructions are you referring to? Please provide a URL.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>