Deadcode_Tr13.WAgame (12.11 kB)
dc 28 fancy tas xd

That's my older TAS, made on 2004-05-14. I did better since then: [attachment=1]
And here's my whole progression from 39.78 seconds to 24.02 seconds: [attachment=2]

This bug was introduced by a fix in v3.6.31.2b:

• [DC] When an Indian Nuclear Test (2 poison points) was used right before the onset of a Sudden Death Nuke (5 poison points), the loss of health due to poison was applied twice (once after the Indian Nuclear Test and again after the Sudden Death Nuke). Both times only the Indian Nuclear Test's 2 poison points were applied, ignoring the Sudden Death Nuke's 5 poison points on that turn and subsequent turns. The fixed behaviour is now to add the poison points (2+5=7), applying the cumulative poison only after the Sudden Death Nuke and not between the two nukes.

This fix had the unintended consequence of introducing the bug seen in this replay.

I'll have to be careful when fixing this fix, because otherwise I might end up introducing yet another related bug!

Thanks j0hny! Using your replay I repaired pizzasheet's replay: [attachment=1]

I still need to do more research to understand what's causing this, but this is a big help. (I've repaired 4 similar corrupted replays, but this one was corrupted in two places and in a way that goes above and beyond what I saw in those 4 replays.)

Cheers,
Deadcode

This replay was brought to my attention due to an apparent disconnection (Anubis) happening without the disconnection itself being recorded, just the auto-surrender of the team...

Anubis, may I please have your replay file of this game?

And, anybody else who was in this game — may I please have your replay file too?

Thanks, pretty sure I understand the rules perfectly now and have no further questions

I can write down you're not allowed to knock the mine after dropping it at the start.

No need to add an extra rule. You could just change

- Place a mine on the cyan block at the top left.

into

- Place a mine on the cyan block at the top left (such that it is resting there when your next turn starts).

and maybe there's even a better (shorter, simpler) way that I can't think of right now.

Yeah Deadcode, use your intuition in some way combined with pseudo-logic sience 

I could do that, but then I'd basically be forced to put my most conservative interpretation of the rules into effect, and might be disallowing myself from doing something that the challenge's author would have been fine with had I only asked.

People think differently. There's no reason to assume that the decisions I'd make about rules would be the same as the challenge author's.

Also, happy new year.

Thanks, you too!

Thanks, got them. And it turns out I was completely wrong about it being a desynchronization problem. It appears to be a network-related problem.

The replay files don't give me enough information to figure out what happened in a case like this. Could you please record a game session using Wireshark and send that to me? http://worms2d.info/Recording_a_packet_log — if you can get your friend to do this at the same time, it'd be even better.

It sounds like you are experiencing desynchronizations. This is almost certainly due to one or two settings being different on your end and your friend's end: Rope Knocking and/or Blood Amount.

When joining a game via WormNET it is not possible for these settings to be out of sync, because they are associated with what channel you enter (#AnythingGoes, #PartyTime, etc.) but with Direct IP, sync of these two settings is not directly enforced. We've taken some steps to make W:A less likely to let these settings go out of sync, but apparently it hasn't been enough because people have still been experiencing these types of desynchronizations.

Here's how to avoid it: When playing Direct IP games, always have the host host W:A either on WormNET or by using a "wa:host" URL ("wa:host?Scheme=Pf" for Rope Knocking=100%, "wa:host?Scheme=Be" for Blood Amount=100%, "wa:host?Scheme=Pf,Be" for both) and then have the host type the "/url" command to put a URL for clients to join in their clipboard, which they can then paste to each player they invite to join their game as a client. This method gives the game a Game ID which W:A checks to make sure all sides used the correct URL.

The host should not host the game by clicking "Direct IP" with no IP address entered in, or by launching W:A with a "wa://" URL. This method results in a blank Game ID which allows Rope Knocking and Blood Amount to be out of sync. (And clients should not be able to join the game by entering the host's IP address next to the "Direct IP" button and clicking "Direct IP".) A WA URL can be launched simply by "running" it using Start -> Run.

I intend to fix this issue in the next W:A Update, but in the meantime, hopefully the above solution is one you and your friends can use.

BTW, I don't know anything about Hamachi. Does it integrate with W:A in any way?