@LilSaadt

WORKING ON COMPLETING THE GAMELOOP!

I dont wana leak too much but since ive got done a lot of tabs, in the next few days the gameloop should be finished, than its just polishing and making it work. Than finally making the game UI actually look good

really basic work on the actual webapp, and the match engine. SO MUCH MORE WORK TO DO. Currently trying to finish the team management, basic transfer logic, and overall game loop. Than we can start making it spicy.

Well due to many issues with the platform and previous project ive had to make a very big switch to a different project i planned to start, really sad I couldn’t get to complete the original one, but Ive came back from vacation and got straight to work, enjoy the sneak peak, WAY more to come soon!

More regular scripting and work on the actual framework, here’s a lil sneak peak at future UI.

New project I was working on, check this small menu concept!

Currently building the bare bones, such as fps framework, drone framework, and other things like environment and maps, than Im going to put it all together into a small test game. (hopefully)

Orbit Bot — Dev Log

Built a simple Slack bot that pulls in space-related APIs and adds a bit of personality on top of them.

What’s in so far

The bot runs on Slack Bolt (Socket Mode) and is wired up with a handful of slash commands and one mention handler.

/nasapic pulls the NASA Astronomy Picture of the Day and displays it with a formatted Slack block (image or video depending on the response type)
/orbitfact returns a random space fact from a small built-in list
/orbitoracle gives a randomized “cosmic answer” for fun decision making
/orbitcatfact pulls live data from the Cat Fact API
/orbitlaunch simulates a multi-stage launch sequence using timed message updates
/orbitping checks responsiveness and returns latency
/orbithelp lists all available commands in a clean help panel

APIs used
NASA APOD API (Astronomy Picture of the Day)
Cat Fact API

Both are pulled using Axios and handled with basic error fallback messages.

Structure

Everything is currently in a single file for simplicity. Commands are separated clearly and use Slack Block Kit for formatting.

Environment variables handle tokens and API keys:

Slack bot token
Slack app token (Socket Mode)
NASA API key

What I learned / ran into
Slack Block Kit formatting matters a lot more than expected, small mistakes can break whole messages
Socket Mode makes local testing way easier than dealing with public endpoints
Keeping responses short is important

Dev Log — Orbit Bot 🚀

So I am currently trying to build a small Slack bot called Orbit Bot that shows cool NASA space images and simple space commands, just a fun cozy vibe.

I set it up in Slack, connected it to Node.js, and got it responding to basic test commands like /ping to check if it’s alive and learned how to call API’s like for cat images.

I learned how bots listen to messages, how APIs send data, and how to fix things when nothing shows up (which happened a lot at first).

Next steps are adding more space commands like planets, random facts, and maybe daily space images so the bot feels more alive and fun to use. (Also designing the bot aswell)

Dev Log — Orbit Bot 🚀

So I am currently trying to build a small Slack bot called Orbit Bot that shows cool NASA space images and simple space commands, just a fun cozy vibe.

I set it up in Slack, connected it to Node.js, and got it responding to basic test commands like /ping to check if it’s alive and learned how to call API’s like for cat images.

I learned how bots listen to messages, how APIs send data, and how to fix things when nothing shows up (which happened a lot at first).

Next steps are adding more space commands like planets, random facts, and maybe daily space images so the bot feels more alive and fun to use. (Also designing the bot aswell)