There is a bug in the main.js onced fixed ready to go!

I am debugging it allllll

I took the ZeroScript architecture, stripped out all the Roblox and MCP stuff, and rebuilt it as Xraps Maths – a browser extension specifically designed to tackle Sparx Maths homework.I made it work with both Gemini and DeepSeek by creating separate provider adapters for each, so I can choose whichever AI I prefer.I built a background service worker that handles screenshots and cross‑tab communication, so Sparx can send a question to the AI tab and get the answer back.I added a “Solve this question” button on Sparx that captures the visible question and automatically sends it to the connected AI.I wrestled with connection issues and retries, so I added robust retry logic and a short delay to give the AI page time to load before pasting the screenshot.I set up a broadcast system that syncs the answer across all open Sparx tabs, so every panel updates instantly when the AI responds.Finally, I optimised the speed, reduced the paste delay, and fixed the UI so the answer appears on Sparx immediately – no more switching back and forth to see if it worked.

(credits to my friend’s account)

So I’ve been building this browser extension called Xraps Maths it’s basically a sidekick that helps me solve maths homework without having to copy‑paste or switch tabs like a maniac.I started with some existing code from another project (ZeroScript) but stripped out all the Roblox/MCP stuff because that’s not what I needed. I kept the smart bits the provider system that can talk to different AI websites and reshaped it into a maths‑solving assistant.What’s already working:I can load the extension into Chrome, and it pops up a little panel on Gemini and DeepSeek.I click “Start”, it injects a system prompt that tells the AI to speak in a special format (with ###XRAPS_ANSWER### blocks).I tested it with something like 3x + 7 = 22 and Gemini actually gave back the answer in the right format so the communication works.There was a bug where the panel got stuck on “Reading answer” even though the AI had already replied but I’ve been tweaking the DeepSeek adapter to fix that (I updated deepseek.js myself).Now I’m pushing it further:I want the extension to also work on Sparx Maths that’s the site where I actually see the question. Instead of making myself copy the question and paste it into Gemini, I want a single button that:Takes a screenshot of the visible question on Sparx.Automatically sends that screenshot to whichever AI I have open (Gemini or DeepSeek).The AI solves it and sends the answer back.The Xraps panel shows the answer + working, right there on Sparx.So I’m basically building a bridge: Sparx → screenshot → AI → answer back to Sparx, all without leaving the page.The new stuff I just added:A background script that does the screenshot magic and talks across tabs.A Sparx‑specific provider that adds the “📸 Solve this question” button to the panel.Cross‑tab messaging so Sparx can ask Gemini/DeepSeek to solve a question and wait for the answer.What’s still a bit sketchy:DeepSeek doesn’t support images, so screenshots sent to DeepSeek will fall back to just the question text (which might still work for text‑based questions).The Sparx DOM is unpredictable the selectors I used might need tweaking if Sparx changes their layout.The answer parsing bug I saw earlier might still bite me (but I’m already on it).Overall vibe:I’ve got a solid foundation the AI providers work, the panel shows up, and the screenshot pipeline is set up. Now it’s about testing it on real Sparx pages, ironing out the rough edges, and making sure the answer shows up cleanly.I’m basically building a maths‑solving cyborg that lives in my browser pretty cool, honestly. 😄

So far we have build the welcome tab and background and timing has been set!!

I Have completed making my personal site!

My pr0gress s0 far!!!

I worked on the ending of SCOUT: Recon Run today.I added a proper mission-complete state so the game knows when the player reaches the objective instead of just letting them keep driving around.I also added a completion screen with a short celebration effect and sound, and started working on making the game return to the menu afterwards so the player can replay the mission.I had a few issues with the UI overlapping the rover and the different game layers, so I had to experiment with where things were drawn in the main game loop.It was a small change, but it made the game feel much more like an actual complete mission rather than just a rover driving around a map.

I FINISHED THE GAME

I finally finished the SCOUT demo game.

The idea was to take the original SCOUT rover project and turn it into something people could actually interact with instead of just looking at the physical prototype.

The game now has:

• A playable SCOUT rover
• An objective/mission system
• NPC characters
• Dialogue
• A medicine delivery mission
• Pixel-art characters
• Sound effects
• Confetti and a mission-complete screen
• PC controls
• Mobile touch controls

One of the harder parts was getting the controls to work properly on both PC and mobile. I originally had the dialogue working with keyboard input, but getting tapping to work reliably took a lot more debugging than I expected. I ended up using pointer events so the same input system could handle mouse clicks and touchscreen input.

I also had to make the dialogue UI adapt to different screen sizes. On mobile, the text box needs to be smaller and the text needs to wrap properly, while on PC there is more space available.

This was also my first time making a proper playable game around one of my hardware projects. A lot of the work wasn’t just writing the game itself, but connecting all the different systems together so that the game actually felt like one thing.

It’s finally playable now, so I’m going to move on to testing it on different devices and fixing anything people find.

🔥

First SCOUT Game Prototype

This was the first version of the SCOUT game simulator.

At this point, I had the basic SCOUT rover moving around the screen and some simple walls to drive around. The idea was to make a small digital version of the rover so I could experiment with how SCOUT would actually work in an environment.

It was pretty basic at this stage, but getting the rover movement working was an important first step. From here, I could start building the actual environment and eventually add things like objectives, characters and missions.

This was basically the starting point for what eventually became the full SCOUT demo game.