[Devlog #3]

Update

• Implemented the functionality of the previous static UI. Now the progress bar UI and the overhead UI is dynamic following User Data.
• You now can Breakthrough to go to Higher Realm.
• Added SFX for breaking through.

Info

• Realm increases player qi gains.
• The higher the realm, the higher the qi gains.

P.S. The Overhead UI currently added above the current user (local), other player won’t have the Overhead UI for now. I’ll work for new feature first before fixing that.

[Devlog #2]

New Content

• Added New Progression Layer: Realm
• Added Progress Bar UI for Realm (Not yet dynamic)
• Added Overhead UI for Player Current Realm and Username (Not yet dynamic)

Bugfixes

• Fix user detection enter an area (the big transparent box); The Box is an Area that gives qi per second when entered.

Devlog #2

I added a new section called Galery Section. I put my favorite wallpaper there so everyone can see it.

Devlog #1

I created this simple website that uses html and css, i spend my time mostly exploring the animations stuff to create an animated border for the Header in the Web! Its not quite smooth but Im satisfied with it since i made it within an hour!

[Devlog #1]

I learned the basics of Roblox Studio, Plugins, making UI in Figma in this first 12 recorded hour. Theres not much yet because im just trying to set up the project and familiarize myself with the language.

I use wally for depedency manager and github for versioning. I just wanna learn new stuff here, so don’t expect a fully polished game at the end. I Can only hope that i have the work ethics to finish this project (Having a proper game loop).

Im making a program that fetch NASA API to get a beatiful image and automatically change my wallpaper.

And my first idea was fetching APOD (Astronomy Picture of the Day) and then automatically change my wallpaper everyday. But before im even working on the automation, the first APOD i got has a very low quality image (960px wide image)…

I’ll be trying other way to get the better NASA images other than APOD

[DOCUMENTATION]

I’m upgrading the documentation for my RanDK Slack Bot by writing a comprehensive, production-ready README file from scratch.

The default tutorial notes were scattered, so I wanted to create a clear guide that details our /rdk-* slash commands, the exact Slack API scopes needed, and a step-by-step local setup process.

I also mapped out a dedicated troubleshooting matrix for common Bolt framework errors and added production hosting instructions for running it 24/7 as a systemd service on Nest.

P.S. The bot is live on the server! Feel free to try it in HackClub Slack

[REFACTOR]

I’m refactoring my RanDK Bot to break apart that giant, messy index.js file from the default tutorial.

Cramming the bot config, external API calls, and individual commands into one place made the code a total headache to expand and super easy to accidentally break.

I split everything into dedicated folders for configs, services, and controllers, turning the main file into a clean switchboard that just links them together.

Now, if one command goes down, the rest of the bot stays online 24/7 on Nest, making it way easier to safely add fun new features in the future.

P.S. The bot is live on the server! Feel free to try it in HackClub Slack

• /rdk-ping
• /rdk-joke
• /rdk-catfact

v0.0.0

Waiting for Nest Hosting approval…