Enigma Simulator

COMPLETELY FINISHED. A big bug that i hadn’t noticed before (because i didn’t type huge messages) is that the rotate rotor logic was wrong. Last rotors wouldn’t seemed like they would never move. What was happening was they were moving every time before. Idrk how to explain it, but the fix was that you only check rotor at position i if rotor at position i-1 moved. then i added the whole cookie logic so you can actually keep the rotor positions without leaving the tab open. And because i added cookies, i also had to add a reset rotor button. Also i added the instructions page. Done now!

FINISHED (most of) THE PROJECT!! Now you can acutally see the plugboard pairs, u can reroute them if you make a mistake. Only thing i need to do now is make an explanation page that says how to use the tool cause honestly if u don’t know how the enigma machine works u probably wouldn’t know what the hell is going on.

Made the Rotors better. Now you can choose how many rotors you want using the slider and choose the rotor by filling in the box!

If you want to send multiple messages without resetting rotor position, you can do that now! you can delete the plaintext and start typing a new message and the ciphertext will reflect that! I spent some time on trying to make typos work(you typed wrong letter so you delete it and replace) but this doesn’t work because then the program uses wrong rotor positions (and this is historical, no way to fix it). Theoretically you could turn the rotor BACK by how much they delete but that’s just not worth it. If you can’t type that’s a u problem. Also, instead of using the plaintext itself as a queue and removing from it, i am using a position variable that indicates up till where you have calculated the ciphertext till. This way you can still see the plaintext when you copy the ciphertext.

I made the input method better. Basically, now it will calculate the encrypted method every key press, but then we can’t necessarily keep up, lets say user copy pasted a message or maybe is just typing fast(bc we use animation) we won’t encrypt everything. So my first idea was to encrypt everything in the input box every time we press new key, but that doesn’t work becaus then it say the user puts in the alphabet, we will consider the message aababcabcd which is wrong. So then i thot, lets keep a track of what is the longest message that we know they have entered and only calculating the new part. Once enter is pressed, clear out plaintext. However, that doesn’t work because there are conflicting accounts of “latest calculated string” so it fails on fast type. I think the problem there was something to do with requests being handled on sepereate threads. What i finally did, is for once in my life found a practical implementation of datastructures. I implemented a queue directly into the plaintext and a flag to see is stuff being handled rn. If yes, you don’t do anything because your character wiill eventually get processed as part of the queue. If no, then start the queue, and if new characters are typed they will be added too.

Made lampboard! it looks kinda bad rn but i am hopping to ad an animation and maybe make the padding round somehow. However, i need to first focus on plugboard, keyboard, maybe rotors animation.

Removed the reversed alphabet. Honestly, idrk what else i was tryna do but i did a bunch of cleanup and then it didn’t work or smth

It’s working “Yay!” basically the problem was that i wasn’t shifting back when exiting a rotor. lets say user typed ‘A’. When you enter rotor 1, you don’t enter wire ‘A’, you enter wire ‘A’+position. Lets say the output of wire ‘A’+position is ‘B’. You can’t input ‘B’ into rotor 2, you have to input ‘B’-position because you need to shift back so that you can factor in the position of rotor 2. That was hella confusing but idrk how to explain it that well

Dealing with scope errors right now and it’s hella annoying cause according to w3schools, if i declare it as var, it will automatically be accessible inside the function which doesn’t seem to be teh case. Btw, i used small python script to generate a reveresd alphabet for each rotor, that denotes the path when going back through the rotor. I will probably still need to debug the logic for doing this backward alphabet, but the changes will be in python file now. This way the js file stays clean

I tried to implement the whole thing, but right now, even though it’s scrambling into a letter, the decryption is not working. Enigma machine is supposed to be, lets say you used rotors 1 0 and 4, with no leads, then typed “HELLO WORLD” and got “XERCL DSOPL” then somebody else should be able to use rotors 1 0 4 and type “XERCL DSOPL” to get “HELLO WORLD” but right now it’s not working

Finish the setup, now i am moving on to the actual encryption. AKA, the plugboard, rotors, reflector, rotors, plugboard sequence. Also, i finished the plugboard logic.