@panther right on . I’m glad it’s working ok for others. The switch from firefox to Brave and the ubuntu update only thing I can think of that changed on my end.
Thanks again for all that you do :grin: :+1:
I’m encountering a bug so weird I feel like I’m forgetting something…
1 defending Japanese infantry in Sumatra.
I land 2 infantry and fly in 4 fighters. The game rolls 2 dice for the infantry and 1 for the 4 fighters. I would prefer if it rolled all 4 dice… Anybody seen this before?
Here’s the file:
@lennardf yea it seems like one to me. I haven’t noticed it before. I saw the fighters move was undone and then redid, but that shouldn’t matter. Maybe undoing and then moving one at a time to reattack triggered it ? idk but it shouldn’t do that regardless.
I’d make a bug report https://forums.triplea-game.org/topic/1708/how-to-submit-a-bug-report
Edit
I guess this should move to triplea support
@barnee yeah seems like a new one to me as well
One thing to point out is that the origin of the error goes back to between round 4 and 5.
In round 4 ANZAC lands three planes on the US carries during combat movement. By ANZAC 5 those three fighters are already corrupted. If you open the game file at the start of ANZAC 5 or any point thereafter, you’ll noticed that if you try to move one of those fighters, the little movement space counter says 1/0 rather than 1/4, as in, these fighters have 0 total movement capacity. (although oddly you can still move them)
Interestingly, in round 5, two of the fighters attacked undefended transports, an action which is an auto-kill and doesn’t require an actual dice roll and disguises that they were already corrupted at that point.
The one fighter which came from Queensland on round 5 to join the fleet is uncorrupted, which is why it’s the only one able to attack Sumatra on round 6.
I tried for a while, but I’m still unable to replicate the error. Hopefully that narrows down the origin though.
BTW I pulled the older game files from here:
https://www.axisandallies.org/forums/topic/38121/x-generaldiarray-vs-lennardf-bm-bid-22/10
@contango ok well not that it should matter or planes should ever get corrupted in this manner, but that initial move of the 3 fighters to a carrier during combat is an illegal move (which is probably why it’s never been spotted before) @LennardF i would def add this information to your bug report :)
Thanks all, bug report submitted.
@Barnee - I had originally moved all 4 fighters into Sumatra at once - the one at a time maneuver was we me trying to work around the bug.
@lennardf i would try to edit the units out and back in assuming you can without breaking your game continuity that should clear whatever the problem is
@ubernaut Had to back up a little but that solved it. Feeling a bit dumb that I didn’t think of that myself - thanks!
@lennardf glad i could help :)