So, that's it so far. No, it's not done. I dare say not even close. At the bottom left you can see the oscillator with an external pause and internal stop button, the light-blue circuit is a 4-bit Adder with decoders, the light-green is an 8-bit simplified general-purpose registry, the purple is a serial-to-parallel shift circuit, the dark blue is the beginning of an ALU, and up the top is the RAM. (Only need 4 bytes right now, it's going to go up to 8. Maybe 16, probably not though.)
I am, in case it was not blatantly obvious, not experienced with this by any means. I have *some* experience with complex-ish circuitry, but none with computer-specific circuits.
What it does so far: Runs on a 2-second delay interval for debugging. I've made a simple I/O button that can turn on one bit in the general purpose registry, which then gets sent to the shift memory which atleast looks pretty cool. ALU has 1 finished bit, so I guess you could do 0+1 if you could be bothered to make an I/O for it.
What I want it to do: Well, it'll probably just be a calculator. A big-ass calculator. With it, you could program in instructions such as "CLOSE BRIDGE_DOOR" (actually I think you need an 8-bit computer to do that) or make it like, automatically seal flooded areas or begin charging the evacuation pod once _x_ rooms are flooded. It probably won't do much more than that, if even that. Even if it could support a decent-sized block of light components for hope of displaying 16x16 resolution nudes (it cant) lag would probably catch up to it eventually. (Lag is fine, for now, but it's not doing any maths yet and god knows what stuff like overflows or burn outs might do)
But yeah. I don't know what I'm doing. If anyone would like to point out anything, test it, help with it, or criticize me for spending an hour and a half of my free afternoon on making computers within computer games, do let me know.
EDIT: I made a crummy gif.
Spoiler