@Red0x

LOST SIGNAL –  LAST - Devlog 

this part was actually annoying I finally got all the signals connected and working properly.I had problems with pretty much every signal. Some buttons weren’t taking me to the right page, some links were broken, and a few pages just wouldn’t load properly on GitHub Pages.At one point I decided to just delete all the files from the repo and start over instead of trying to fix everything one by one.I added the project folder again and then separated and uploaded the files one by one. That made everything way easier to manage because I could actually see which files were there and which ones weren’t.I also had some problems with uppercase and lowercase letters in the file names. I didn’t realize how much that could mess up the links. A file could be there, but if the link used a different capitalization, GitHub Pages wouldn’t find it.So I went through the links and made sure they matched the actual file names exactly.After fixing all of that, I finally got the whole thing connected:Signal 01 -> Signal 02 -> Signal 03 -> Signal 04
And now… Signal 04 is finished too.
Honestly, getting all the puzzles to work was only half the problem. Making all the different pages connect properly was a whole challenge by itself.But it’s finally working.
No more broken links.No more random missing pages.No more GitHub Pages confusion. The whole signal chain is connected now.

LOST SIGNAL IS BACK ONLINE.
SIGNAL 01 -> SIGNAL 02 -> SIGNAL 03 -> SIGNAL 04
PROJECT COMPLETE.

😁😁

Final Devlog — LOST SIGNAL
And yeah… I think LOST SIGNAL is finally done.This project started as a simple idea for a puzzle website, but it ended up taking way longer than I expected. I built the pages myself with HTML and CSS, and then added JavaScript when I wanted the puzzles to actually react to what the player was doing.The first signal was probably the part I spent the most time messing around with. I had the code 18 - 5 - 4 - 24 , and the idea was that the numbers weren’t really numbers. After getting the first puzzle working, I added the wrong-attempt system, hints, and eventually the continue button that takes the player to the next part.Then came Signal 02.I wanted it to feel different from the first puzzle instead of just being another text box. The player has to use the numbers from Signal 01, find the right boxes, and then figure out what the message means. I also connected the later clues to my own website, which made the whole thing feel more like an actual trail instead of separate random puzzles.Honestly, I broke things a lot while making this.There were times when the CSS looked completely wrong, buttons didn’t look like buttons, pages didn’t match each other, and some of the JavaScript didn’t behave the way I wanted. I also kept changing small design things because I wanted the site to feel like something I actually made instead of a random template.The biggest thing I learned was that making a project isn’t just writing code until it works. A lot of the time was spent figuring out why something didn’t work, changing it, testing it again, and sometimes realizing that my first idea wasn’t even that good.I also got much more comfortable with HTML, CSS and JavaScript during this project. Before starting, I didn’t really understand how much the different parts of a website could work together. Now I can actually build a page, style it, add interactions and connect multiple pages into one project.LOST SIGNAL isn’t some huge game, but I’m genuinely happy with it because I made it myself and I learned a lot while building it.
So…SIGNAL LOST.
PROJECT COMPLETE. 
Thanks to everyone who helped me when I got stuck.

LOST SIGNAL — CSS ImprovementsToday I mainly worked on improving the CSS of LOST SIGNAL.I changed the overall look of the signals and made the backgrounds feel more connected to the mystery/puzzle theme. Signal 01 and Signal 02 now have their own slightly different styles instead of looking exactly the same.I also cleaned up some of the spacing, borders, buttons and puzzle boxes so everything fits better on the page. I kept the grid effect in Signal 03 and the game area because it actually fits the design, but removed some of the extra lines that were making the page look too crowded.I also made sure the design still feels like LOST SIGNAL instead of making it look like a random website template.Next, I want to move forward with Signal 04 and keep improving the project as I go.

LOST SIGNAL — Signal 03
Signal 03 is finally starting to feel like an actual game instead of just a bunch of questions.I’ve finished the first part of the Signal 03 puzzle chain. It starts with a riddle, then moves through a few different steps before leading the player to a real-world location.After that, I started working on the first actual mini-game.The player has to cross a signal area while avoiding moving obstacles. I made the player start at the bottom and the exit at the top, with multiple lanes and obstacles moving in different directions. There’s also a timer, so you can’t just stand there forever.I also ran into a pretty annoying JavaScript problem where the WASD controls were blocking letters inside the answer boxes . I fixed that by making the controls activate only when the mini-game is running.The whole Signal 03 mini-game is staying inside the same , file instead of making a bunch of separate pages.There’s still a lot more planned for Signal 03, including another puzzle, a hidden clue, and a memory game.Signal 03 is definitely getting bigger than the first two signals.

LOST SIGNAL - Signal 03
Location Section Done Signal 03 is moving forward.I finished the location section and connected it to the main puzzle chain. The coordinates now lead to a city, and then another clue reveals the next location.I had a small stupid bug while testing because I accidentally put some Signal 03 code into the wrong file  but I fixed it and everything is working now.No answers or spoilers here.
Next: Mini-game

LOST SIGNAL - Signal 03 JavaScript Done Signal 03 is finally working now.I finished the JavaScript for the main puzzle chain. The riddle works, the equations unlock one after another, and the final coordinates appear after solving them.This part took a bit of testing because I wanted each puzzle to unlock only after the previous one was solved.The main Signal 03 puzzle is now working, so next I’m moving on to the location section and the mini-game.No answers or spoilers here.Next: Location section -> mini-game

LOST SIGNAL - Signal 03 HTML AND CSS DONE

Signal 03 is finally looking like an actual part of LOST SIGNAL now.I just finished the whole HTML and CSS for Signal 03 together. This one is much bigger than the previous signals, so getting the layout and design done took a while.Now I’m moving on to the JavaScript and actually making the puzzles work.No answers or spoilers here
 Next: JavaScript

LOST SIGNAL - Signal 03 HTML DONE finally finished the whole HTML for Signal 03 at once, which is the third puzzle stage of LOST SIGNAL.This one is going to be a much bigger part of the project compared to the previous signals. I’ve finished the basic HTML structure, and now I’m moving on to the actual logic and puzzles.Next I’m going to work on the JavaScript for the puzzle stages, then the coordinate part, and after that I’ll start building the location-based section. I also want to add a small playable mini-game and another puzzle after it, so Signal 03 doesn’t just feel like a bunch of questions.I’m also planning to connect everything together so the player has to actually notice things and figure out what to do next instead of just entering random answers.I’m not sharing the answers or the actual puzzle solutions here because that would completely ruin the point of the project Signal 03 is still being built, but the main HTML structure is finally done.Next: JavaScript -> puzzles -> location section -> mini-game -> more clues.

Completed the signal02
It took me long time to get through the grid box in html then i went to CSS to style the box then , I hopped to js to get the message box and to make the grid really work also after clearing the grid stage i added my site for one of the puzzle stage including my instagram ID:D

Today I finished Signal 02.I first made the Signal 02 page and added the message for the player. There is nothing to decode in this one, so the player has to look somewhere else.I also added the continue button and made it go to learn.html.Then I went back to Signal 01 because I wanted the player to only be able to reach Signal 02 after actually solving Signal 01. So I added another continue button there which stays hidden at first.After the player enters the code and gets ACCESS GRANTED, the continue button appears. Clicking it takes them to Signal 02.I also made a separate CSS section for Signal 02 so I could change its design without messing up Signal 01.Had a few stupid mistakes while doing the JS , like putting the script stuff in the wrong place, a typo in getElementById and forgetting to add the result element. Fixed those and now the flow works.Signal 01 -> solve ->ACCESS GRANTED -> CONTINUE -> Signal 02Next I can continue building the next part.

LOST SIGNAL — Signal 01 CompleteI finally finished the first puzzle of my game, LOST SIGNAL.The first puzzle is pretty simple, but I wanted it to feel like an actual signal instead of just a normal question.The player gets this:**13 - 1 - 19 - 11 **The clue says that the numbers aren’t really numbers. The player has to figure out that they represent letters using A = 1, B = 2, C = 3…That gives:13 = M1 = A19 = S11 = KSo the final answer is mask. (BUT OBVIOUSLY I CHANGED THE WORD)I also added different hints depending on how many times the player gets the answer wrong. And after 12 wrong attempts, I added a little message because why not Signal 01 is now finished.Now I’m moving on to Signal 02, where I want to make things much more interesting and have the player move through multiple pages to find clues.

LOST SIGNAL DEVLOG #2 I worked more on the first version of LOST SIGNAL.I started building the actual website using HTML and CSS. The basic game layout is now there, including the signal section, clue, answer box and decode button.I also worked on the visual style. I didn’t want it to look dry or a boring website, so I went with a darker blue and gray look with some small interface details.It’s starting to feel more like an actual game now instead of just a normal webpage.Next, I want to work on the first puzzle and make the interactions actually work.

LOST SIGNAL DEVLOG #1 I started working on a new project called LOST SIGNAL.It’s going to be an interactive puzzle game where you have to find clues, solve puzzles and figure out what is actually going on. I’m making it with HTML, CSS and JavaScript.Right now I have the basic files set up and I’m planning out the first puzzle, right now i am just creating the first puzzle!I don’t want it to be hard or boring, so anyone should play and solve them by paying attention and thinking.

I’m working on my Slack bot, Rubber-Rubber Bot.I added a few commands like ping, help, hello, about, 8-ball, and random facts. I also finished the README and pushed the project to GitHub.Next I’m trying to get it running 24/7 on Hack Club Nest.

I finally finished and shipped my personal website!I started by setting up the basic HTML structure and then worked on the styling with CSS. From there, most of the time went into experimenting with the layout, spacing, typography, backgrounds, cards, and especially the overall visual feel of the site.One of the things I spent quite a bit of time on was the profile picture. I didn’t want the usual perfectly circular profile picture sitting in the middle of a card, so I experimented with making it slightly tilted and giving it more of a “popping out” look. Getting the position and sizing right took a few tries. 😭I also experimented with the site’s colour direction and overall atmosphere. I tried different ideas before settling on the final look. I wanted it to feel modern and digital without making every single part of the website scream the same colour.The website also has sections about me, my interests, and the things I work on. I kept the content fairly simple because I wanted the actual design and personality of the site to do some of the talking.After finishing the frontend, I organized the project files and prepared everything for GitHub. I added the HTML, CSS, images, and README, then set up GitHub Pages so the website could actually be accessed online.Getting it deployed was another small adventure. I initially ended up with a GitHub Pages URL that included the repository name, had to figure out how the Pages setup worked, and eventually got the site working on my main GitHub Pages URL.The whole build took around 2 hours and 52 minutes, which is a lot faster than my previous attempt at making a personal website. That was probably one of the coolest parts for me — I could actually feel that I was getting faster at building and figuring things out.This project wasn’t about making the most complicated website possible. It was mainly about taking an idea, building it myself, experimenting when something looked wrong, fixing things, and actually getting the finished project online.And now it’s live.