I really hate doing this one as the manual guy, but I love the soothing sounds when I'm defusing the bomb!

@smeggingimboid -- before the Two colors opposite rule is the "At most one color flashed out of red, yellow, and blue". Since your sequence was POG, the rule I listed before applies. At most, one (in fact, 0, which is less than 1) of those flashed, which makes it true.

@Timwi I managed to find out that the module sequence i had flashed Purple Orange Green and the rule should of been the two colours opposite but when i went to press the correct colour it gave me a strike because according to the log file it should of been: One colour flashed out of red Yellow and blue. Pretty strange also the link to the log is here :https://ktane.timwi.de/More/Logfile%20Analyzer.html#bomb=XN6EC9

@Timwi Odd, I have not been able to recreate this. I assume there was something wrong with my program (I'm writing code in java to solve KTANE modules, this happened to be one of them). Sorry for bothering you. Thanks for all of the modules you have made for this game! I'm hoping to be able to code solutions to many of them!

@Friends99 That is not the case. If blue flashed twice, the “at most one primary” rule still applies.

@Timwi Thakn you, I managed to figure it out. I was unaware that the primary rule was ignored if we used the same primary twice. That was my issue. Thank you.

@Friends99 I’ll need the logfile to investigate this problem. If you could contact me on Discord and send me the logfile, that would be great. However, I strongly suspect that you may have run into a bug that has been fixed, as I submitted a bugfix just today.

I'm getting a strike on stage one where the colors flashing are blue, purple, blue (they aren't adjacent, not that it matters). I am directed to column A in the smaller table, but entering the first color earns a strike. After screwing around, I have figured out that the module seems to believe I should be following column E, but I can't for the life of me figure out why. The primaries rule applies, so why should we be going to the opposites rule? I have many other simon screams modules on the bomb, is this part of my error?

Timwi, just thinking about this module makes me want to scream

0------------simon
l-ahhhh!
/\

I truly don't understand the manual, is anyone willing to simplify it for me?

Oops my bad. I was referring to "when in stage x take xth color" part. It's too far away from the "consider the whole sequence" statement, and that statement applies only within that particular radio button anyway.
So xth color of which sequence now?

@Jerry Cheng — You lost me. You don’t seem to be talking about ambiguities in the manual anymore. An ambiguity is something that can be interpreted different ways and thus be misunderstood. I appreciate your suggestions, but I don’t really see how they make it any clearer: 1. Those two sentences refer to separate steps in the process to find the solution. They definitely should not be in the same sentence. They’re still part of the same bullet point though. 2. It is not the manual’s fault if you make an incorrect assumption. The manual tells you how to solve the module, it shouldn’t have to also tell you how not to solve it. For example, the vanilla Wires manual doesn’t separately tell you that you never need to cut more than one wire — it’s already implied by the instructions.

1. “At each stage, consider the whole sequence of flashes.” should somehow be closer to that 'at stage x, take x letter' instruction, preferably in the same sentence.
Currently there's no indication, visually or logically, that the two sentences go together. One is the starter of a block of text, the other a tip-like instruction that's on top of another section.

2. non of these conditions is concerned with the sequence itself. They are only associated with the bomb. Thus however long the sequence goes, the answer to it is a fixed length unless there's changing indicators or serial numbers.
You might want to confirm this in the guide because people would expect a module resembling Simon Says to have longer answer each stage.

@Jerry Cheng Re 1. It says “At each stage, consider the whole sequence of flashes.” Re 2. It says “Go through that column from top to bottom and press every color whose condition applies.” Which of these is ambiguous, and how would you rephrase them?

keep talking and nobody explodes is a game that will make you break up with your wife/husband. I did this with my mom, and I thought she was gonna toss me out into the street.

The manual has at least two ambiguity:
1. when you say first/second/third color that flashes, does that refer to the first/second/third of the whole sequence, or the particular sub-sequence that meets the requirements of the row?
2. every stage only requires input of a certain length bomb-wise and no more? You would expect a ever growing sequence of action to take on a module named as such.

I'd say it might get easier than the original one since the original one builds up over time and has a totally different set of translation every time a strike occurs (can get really embarassing when a needy causes a strike midway). For this only a small part of the original sequence needs to be remembered, and the rest is just 'offline' processing that will not be affected whatnot.

@Timwi I would appreciate that thank you. I just need to get Discord xD

@ThePlayaJam @Foxy Ze Geek: Feel free to ask specific questions and I’ll clarify the rules. You’re welcome to join us on Discord too and I’ll be happy to do a training mission with you :)

@Sniglett I don’t understand. If you have ≥ 3 battery holders, you necessarily also have ≥ 3 batteries, so both apply. Swapping them makes no difference to this.

Anyone understand the manual??? Me and my friend are trying to figure it out. We were very unsuccessful..... XD

If Simon Says wasn't hard enough, now we have this. I don't even understand the manual there.

>3 Battery holders will never be applicable if >3 batteries is above it. 3 Battery holders means a minimum of 3 batteries total. I suggest swapping those?