Slang for people who aren’t flashlight enthusiasts and would find the complex UI needed to implement all the controls we could enable into a single button interface a bit confusing. Muggle mode is a simplified mode that’s more intuitive and doesn’t need an instruction manual to use.
I agree. Shouldn’t muggles be using $2 zillion lumen Tac lights sold for $50? Personally I think it’s a pointless mode for a light aimed at enthusiasts.
No, they’re using those because they don’t have this and other nice lights. Also: it’s just not hard to add some kind of simplified mode, it’s all code.
One of my EDC lights has a X5/X6 driver, and I keep it at muggle mode because in thoughtless daily use I ’m kind of a muggle myself, in that I need the light to work simple without suddenly blinding someone.
I like the muggle ramp and exit via a button sequence. Second in line the off-low-med-highish-off.
As a side note, I don’t recommend pairing “low/med/high/off loop” and “special sequence of button presses”, since the click-per-mode UI is the most likely for people to accidentally input the six clicks to exit.
That could be alleviated by using an Olight Baton-style UI instead though, where it’s click for on/off and hold to change brightness. Perhaps there should be four UI options instead of three.
Has anyone considered a mini dip switch on the board for selecting things like Muggle mode?
It could not be disengaged by accident, easiest way to operate it would be to remove the head and push with a pen.
We need consistency. The BLF Q8, GT have a 4 click lockout and the Emisar D4 has a 6 click lockout. FW3A a 6 click muggle mode. Maybe we should start giving some frequently used functions a standardized number of button clicks?