|
1033
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792896537.6848469
|
1793760537.6848469
|
|
1034
|
Untitled by @jam06452 | Stardance
|
jam06452
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @jam06452 | Stardance
|
1792781575.711032
|
1793386375.711032
|
|
1035
|
The Ultimate Calculator by @ZM | Stardance
|
ZM
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: The Ultimate Calculator by @ZM | Stardance
|
1792648418.4295447
|
1793253218.4295447
|
|
1037
|
3d can holder by @Microsoft_Bingham | Stardance
|
Microsoft_Bingham
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 3d can holder by @Microsoft_Bingham | Stard Title: 3d can holder by @Microsoft_Bingham | Stardance...
|
1793274947.6185331
|
1793879747.6185331
|
|
1038
|
πKey by @ZiDi | Stardance
|
ZiDi
|
0
|
15.82
|
0
|
[]
|
[{"post_id": 6328, "ts": "2026 [{"post_id": 6328, "ts": "2026-06-10T17:25:48Z", "hours": 3.8253, "text": "Today I added USB Mode to the Pi_Key project, which allows the device to act as a portable AI configuration and data storage system. With this mode, AI settings and chat histories are stored directly on a USB flash drive, making the system fully portable across Linux, Windows, and macOS. The goal is to keep it simple and plug-and-play, so users can move their setup between machines without any extra setup. At the moment, the implementation is still in an early stage. There is no encryption or access protection, which means anyone with physical access to the USB drive can read all stored data, including API keys and chat histories. Security improvements are planned for future versions, including encryption and better protection for sensitive configuration data. Love u :3"}, {"post_id": 4992, "ts": "2026-06-08T17:14:17Z", "hours": 0.4158, "text": "I made a new design for Pi Key, I’ve already ordered it, and now I just hope it actually works. So what do I want to do next? Since I don’t need to work on the PCB for now, I’m going to focus on the software side. I want to make the app faster and smoother, clean up the code, and give it a more professional look. I also want to improve the GitHub repository so it looks well-structured and serious, not messy. On top of that, I want to build a proper website for the project. And if I finish the software in Python now, my next move is to rewrite the whole thing in Rust to make it faster, cleaner, and more solid. Basically: hardware is done for now — time to level up the software, the codebase, and the whole presentation. Love u :3"}, {"post_id": 4399, "ts": "2026-06-07T18:32:34Z", "hours": 0.7658, "text": "Fixing some bugs, repairing history saving love u :3"}, {"post_id": 3700, "ts": "2026-06-06T19:10:18Z", "hours": 3.2453, "text": "Currently working on an AI-powered chat system for Pi Key. Pi Key is evolving into much more than just an API key manager. The device is designed to securely store API keys, passwords, and chat histories while providing direct access to AI conversations. Current features: • AI Chat • API Key Storage • Password Manager • Chat History Storage Planned features: • Encrypted Data Storage • Local AI Processing • File Management • Secure Notes • Plugin System • Multi-Provider AI Support • Device-to-Device Sync • Custom Automations • Developer Tools • Terminal Access Thanks for support Love u :3"}, {"post_id": 2919, "ts": "2026-06-05T20:29:36Z", "hours": 2.2464, "text": "Working on AI API’s keys saving, connecting to openRouter, and some other things"}, {"post_id": 2312, "ts": "2026-06-04T18:50:02Z", "hours": 2.12, "text": "Some sneak pick from the app I’m working on for communication between PC and pi-key. It will also have support for adding API keys and communicating with AI bots and saving history locally. I’m also working on encrypted password storage and I’m thinking about rewriting all the code from this app and also from the software that runs on pi-key from python to rust."}, {"post_id": 1553, "ts": "2026-06-03T17:20:30Z", "hours": 1.2569, "text": "Testing programs on prototype :)"}, {"post_id": 937, "ts": "2026-06-02T18:15:14Z", "hours": 0.8025, "text": "Working on Simple Web-Site For now its just easy animation and repo button but in future I want to use it for something bigger… Maybe I am gonna buy domain for it"}, {"post_id": 894, "ts": "2026-06-02T16:52:16Z", "hours": 0.3511, "text": "Working on README in my repo"}, {"post_id": 283, "ts": "2026-06-01T14:56:08Z", "hours": 0.4242, "text": "Some 3D rendering :)"}, {"post_id": 236, "ts": "2026-06-01T11:12:17Z", "hours": 0.3639, "text": "Working on PCB :3"}]...
|
Title: πKey by @ZiDi | Stardance
Devlogs:
Working Title: πKey by @ZiDi | Stardance
Devlogs:
Working on PCB :3
Some 3D rendering :)
Working on README in my repo
Working on Simple Web-Site For now its just easy animation and repo button but in future I want to use it for something bigger… Maybe I am gonna buy domain for it
Testing programs on prototype :)
Some sneak pick from the app I’m working on for communication between PC and pi-key. It will also have support for adding API keys and communicating with AI bots and saving history locally. I’m also working on encrypted password storage and I’m thinking about rewriting all the code from this app and also from the software that runs on pi-key from python to rust.
Working on AI API’s keys saving, connecting to openRouter, and some other things
Currently working on an AI-powered chat system for Pi Key. Pi Key is evolving into much more than just an API key manager. The device is designed to securely store API keys, passwords, and chat histories while providing direct access to AI conversations. Current features: • AI Chat • API Key Storage • Password Manager • Chat History Storage Planned features: • Encrypted Data Storage • Local AI Processing • File Management • Secure Notes • Plugin System • Multi-Provider AI Support • Device-to-Device Sync • Custom Automations • Developer Tools • Terminal Access Thanks for support Love u :3
Fixing some bugs, repairing history saving love u :3
I made a new design for Pi Key, I’ve already ordered it, and now I just hope it actually works. So what do I want to do next? Since I don’t need to work on the PCB for now, I’m going to focus on the software side. I want to make the app faster and smoother, clean up the code, and give it a more professional look. I also want to improve the GitHub repository so it looks well-structured and serious, not messy. On top of that, I want to build a proper website for the project. And if I finish the software in Python now, my next move is to rewrite the whole thing in Rust to make it faster, cleaner, and more solid. Basically: hardware is done for now — time to level up the software, the codebase, and the whole presentation. Love u :3
Today I added USB Mode to the Pi_Key project, which allows the device to act as a portable AI configuration and data storage system. With this mode, AI settings and chat histories are stored directly on a USB flash drive, making the system fully portable across Linux, Windows, and macOS. The goal is to keep it simple and plug-and-play, so users can move their setup between machines without any extra setup. At the moment, the implementation is still in an early stage. There is no encryption or access protection, which means anyone with physical access to the USB drive can read all stored data, including API keys and chat histories. Security improvements are planned for future versions, including encryption and better protection for sensitive configuration data. Love u :3...
|
1793134117.4251556
|
1793738917.4251556
|
|
1039
|
Animatronics Archive by @Ur_Local_R3N | Stardance
|
Ur_Local_R3N
|
0
|
0.95
|
0
|
[]
|
[{"post_id": 32726, "ts": "202 [{"post_id": 32726, "ts": "2026-07-22T01:51:20Z", "hours": 0.9508, "text": "Been working on this site for about 1.5 years, is going to be an info dump about animatronics, mainly animatronic restaurants, and how to make them. It’s been a long WIP, as when I first started I was learning HTML while working on it so I’ve had to re-start several times due to amateur mistakes. Stay tuned for this mess lol."}]...
|
Title: Animatronics Archive by @Ur_Local_R3N | Sta Title: Animatronics Archive by @Ur_Local_R3N | Stardance
Devlogs:
Been working on this site for about 1.5 years, is going to be an info dump about animatronics, mainly animatronic restaurants, and how to make them. It’s been a long WIP, as when I first started I was learning HTML while working on it so I’ve had to re-start several times due to amateur mistakes. Stay tuned for this mess lol....
|
1792705997.0441976
|
1793310797.0441976
|
|
1040
|
small overtures by @luftacen | Stardance
|
luftacen
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: small overtures by @luftacen | Stardance
|
1792633674.2686536
|
1793238474.2686536
|
|
1041
|
My first slack bot! by @Bri | Stardance
|
Bri
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Bri | Stardance
|
1792666203.30291
|
1793271003.30291
|
|
1042
|
StudyBuddy by @riya | Stardance
|
riya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: StudyBuddy by @riya | Stardance
|
1793282020.4758995
|
1793886820.4758995
|
|
1043
|
Untitled project by @shaurya | Stardance
|
shaurya
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @shaurya | Stardance
|
1792633942.1338084
|
1793238742.1338084
|
|
1044
|
My awesome macropad! by @rae | Stardance
|
rae
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @rae | Stardance
|
1792795769.3790262
|
1793400569.3790262
|
|
1045
|
My awesome macropad! by @MacktheSilly | Stardance
|
MacktheSilly
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @MacktheSilly | Sta Title: My awesome macropad! by @MacktheSilly | Stardance...
|
1792669889.9997706
|
1793274689.9997706
|
|
1046
|
My awesome macropad! by @V | Stardance
|
V
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @V | Stardance
|
1792918261.1914008
|
1793782261.1914008
|
|
1047
|
My awesome macropad! by @Shiven | Stardance
|
Shiven
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Shiven | Stardance
|
1792947000.1208053
|
1793811000.1208053
|
|
1049
|
Hexapod-HomeAssistent by @thebiker_cat | Stardance
|
thebiker_cat
|
0
|
20.89
|
0
|
[]
|
[{"post_id": 12825, "ts": "202 [{"post_id": 12825, "ts": "2026-06-21T00:11:33Z", "hours": 8.0814, "text": "Completed Goals I have reached a few goals and managed to complete a few challenges that I was afraid of. There are actually two important steps I have completed. Build Update First, I managed to finish the raw Hexapod build (a few electronic parts are still missing, but I mean the body). Code Improvements Secondly, I made a few improvements to control a Hexapod leg with coordinates (we also had a problem with our C++ header files that my friend has, thank goodness, solved). So now we are really able to control a real leg with coordinates. Movement Test Another big feature where I laid my focus was a first movement test. I already implemented this feature. I tried to program the tripod gait. I hope that it’ll work, because I wasn’t able to test it until now like I mentioned above, I hadn’t had the time to include some electronic parts in the Hexapod build. What’s Next? I suppose my next big step will be to actually get the robot to walk, so that my friend can finish his important tests and start to implement other movement features, because he is already really hyped for that. We’ll maybe also start with some kind of a control system, but I think that this will take us a little more time and it will be a while yet before we actually get started with that."}, {"post_id": 10235, "ts": "2026-06-16T21:18:35Z", "hours": 8.32, "text": "Progress Since my last devlog, I’ve made great progress. I’ve been looking into inverse kinematics quite a bit and I was pretty successful. I managed to derive formulas for my calculations with a few drawings. I also started to build my robot. Actually, I’ve managed to build up one leg. The leg consists of three joints, each controlled by a servo motor. Implementation Furthermore, my last step was to put my equations into code, so I wrote a test program. Now I am able to convert the angles into coordinates and I can move the leg with coordinates wherever I want. Challenges The biggest challenge so far has been getting the math right for the inverse kinematics, but once I drew the leg and did my calculations on paper, everything came together pretty quickly. What’s next? My next actions would be to make some movement tests. I will try to make a first walking test and see how stable the leg performs. After that, the plan is to build the remaining legs and work on coordinating them together."}, {"post_id": 6733, "ts": "2026-06-11T08:32:11Z", "hours": 4.4881, "text": "I started the Hexapod project by creating a project file structure and tried to implement the first functions for a leg of the Hexapod. It’s a bit difficult right now, because I am still waiting for my project hardware to arrive. So because I couldn’t really start to build the robot, and it was also difficult to start programming it, I started with a few servo tests with buttons and a potentiometer so that I would at least do something to better understand how servo engines work. My next step (when my hardware has arrived) would be to build the robot or at least a leg and try to figure out the kinematics and movement of it and implement it."}]...
|
Title: Hexapod-HomeAssistent by @thebiker_cat | St Title: Hexapod-HomeAssistent by @thebiker_cat | Stardance
Devlogs:
I started the Hexapod project by creating a project file structure and tried to implement the first functions for a leg of the Hexapod. It’s a bit difficult right now, because I am still waiting for my project hardware to arrive. So because I couldn’t really start to build the robot, and it was also difficult to start programming it, I started with a few servo tests with buttons and a potentiometer so that I would at least do something to better understand how servo engines work. My next step (when my hardware has arrived) would be to build the robot or at least a leg and try to figure out the kinematics and movement of it and implement it.
Progress Since my last devlog, I’ve made great progress. I’ve been looking into inverse kinematics quite a bit and I was pretty successful. I managed to derive formulas for my calculations with a few drawings. I also started to build my robot. Actually, I’ve managed to build up one leg. The leg consists of three joints, each controlled by a servo motor. Implementation Furthermore, my last step was to put my equations into code, so I wrote a test program. Now I am able to convert the angles into coordinates and I can move the leg with coordinates wherever I want. Challenges The biggest challenge so far has been getting the math right for the inverse kinematics, but once I drew the leg and did my calculations on paper, everything came together pretty quickly. What’s next? My next actions would be to make some movement tests. I will try to make a first walking test and see how stable the leg performs. After that, the plan is to build the remaining legs and work on coordinating them together.
Completed Goals I have reached a few goals and managed to complete a few challenges that I was afraid of. There are actually two important steps I have completed. Build Update First, I managed to finish the raw Hexapod build (a few electronic parts are still missing, but I mean the body). Code Improvements Secondly, I made a few improvements to control a Hexapod leg with coordinates (we also had a problem with our C++ header files that my friend has, thank goodness, solved). So now we are really able to control a real leg with coordinates. Movement Test Another big feature where I laid my focus was a first movement test. I already implemented this feature. I tried to program the tripod gait. I hope that it’ll work, because I wasn’t able to test it until now like I mentioned above, I hadn’t had the time to include some electronic parts in the Hexapod build. What’s Next? I suppose my next big step will be to actually get the robot to walk, so that my friend can finish his important tests and start to implement other movement features, because he is already really hyped for that. We’ll maybe also start with some kind of a control system, but I think that this will take us a little more time and it will be a while yet before we actually get started with that....
|
1792795967.97154
|
1793400767.97154
|
|
1050
|
My first slack bot! by @rae | Stardance
|
rae
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @rae | Stardance
|
1793303295.920563
|
1793908095.920563
|
|
1051
|
Chat (Not) GPT by @mirrored-chameleon | Stardance
|
mirrored-chameleon
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Chat (Not) GPT by @mirrored-chameleon | Sta Title: Chat (Not) GPT by @mirrored-chameleon | Stardance...
|
1792914545.7412252
|
1793778545.7412252
|
|
1052
|
UV and Ozone Sterilization chamber by @Hirasawa | UV and Ozone Sterilization chamber by @Hirasawa | Stardance...
|
Hirasawa
|
0
|
14.51
|
0
|
[]
|
[{"post_id": 17616, "ts": "202 [{"post_id": 17616, "ts": "2026-06-28T14:19:38Z", "hours": 4.8711, "text": "I worked on the firmware today. Man, I’m exhausted! It took forever! I think I’ll sleep really well tonight. Also, the firmware ended up looking really ugly!"}, {"post_id": 16898, "ts": "2026-06-27T13:05:57Z", "hours": 1.9642, "text": "I made pretty good progress today. The 3D data is almost done, so all that’s left is to write the firmware and so on. I hope it’ll be ready by tomorrow."}, {"post_id": 15020, "ts": "2026-06-24T12:23:42Z", "hours": 1.2764, "text": "Today I built a smaller version of it. I haven’t been able to spend much time on Hackclub lately because of preparations for the cultural festival, but it was nice to finally get back to it after so long."}, {"post_id": 3396, "ts": "2026-06-06T09:37:02Z", "hours": 2.6919, "text": "I’ve finished the 3D model for now. Since JLC3DP is charging an outrageous price, I think I’ll just print it myself using the club’s 3D printer."}, {"post_id": 1355, "ts": "2026-06-03T09:59:07Z", "hours": 1.4042, "text": "I made the door and the back cover. It looks really great."}, {"post_id": 774, "ts": "2026-06-02T13:10:21Z", "hours": 0.8825, "text": "I made the control panel section. It’s starting to look like a microwave!"}, {"post_id": 726, "ts": "2026-06-02T10:11:54Z", "hours": 1.1325, "text": "I drew up a circuit diagram today. I think the internal circuitry should be fine as is, but I’m worried that if the internal temperature gets too high and the case warps badly, that would be a problem, so I’m wondering if I should install a thermometer that can withstand UV exposure."}, {"post_id": 487, "ts": "2026-06-01T23:16:32Z", "hours": 0.2847, "text": "First devlog"}]...
|
Title: UV and Ozone Sterilization chamber by @Hira Title: UV and Ozone Sterilization chamber by @Hirasawa | Stardance
Devlogs:
First devlog
I drew up a circuit diagram today. I think the internal circuitry should be fine as is, but I’m worried that if the internal temperature gets too high and the case warps badly, that would be a problem, so I’m wondering if I should install a thermometer that can withstand UV exposure.
I made the control panel section. It’s starting to look like a microwave!
I made the door and the back cover. It looks really great.
I’ve finished the 3D model for now. Since JLC3DP is charging an outrageous price, I think I’ll just print it myself using the club’s 3D printer.
Today I built a smaller version of it. I haven’t been able to spend much time on Hackclub lately because of preparations for the cultural festival, but it was nice to finally get back to it after so long.
I made pretty good progress today. The 3D data is almost done, so all that’s left is to write the firmware and so on. I hope it’ll be ready by tomorrow.
I worked on the firmware today. Man, I’m exhausted! It took forever! I think I’ll sleep really well tonight. Also, the firmware ended up looking really ugly!...
|
1793213276.7232416
|
1793818076.7232416
|
|
1053
|
My awesome macropad! by @TyrantLizard76 | Stardanc My awesome macropad! by @TyrantLizard76 | Stardance...
|
TyrantLizard76
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @TyrantLizard76 | S Title: My awesome macropad! by @TyrantLizard76 | Stardance...
|
1792928975.7234645
|
1793792975.7234645
|
|
1054
|
Kittypad by @HY | Stardance
|
HY
|
0
|
8.79
|
0
|
[]
|
[{"post_id": 17507, "ts": "202 [{"post_id": 17507, "ts": "2026-06-28T09:59:10Z", "hours": 0.7831, "text": "I created the basic firmware for the Kittypad, I intend to build the ‘game’ after I build the physical macropad so that I am able to test it."}, {"post_id": 1521, "ts": "2026-06-03T16:28:28Z", "hours": 1.6431, "text": "I completed the CAD design for the case! I added a counterbore as well as a 3mm thick border around the top case. I left the left side open as part of my design and to show off the silkscreen. I realised that I had used the wrong LED in my PCB and had to face a bunch of DRC errors, because the footprint comes with a hole, the DRC assumed that there was lack of edge clearance and kept giving me the error, so I just ignored the violation."}, {"post_id": 1442, "ts": "2026-06-03T14:10:47Z", "hours": 3.9331, "text": "Spent a whole bunch of hours fighting Fusion360 to create a base plate. Key features include holes at the bottom in order to put the heat inserts, as well as a drill hole of 3.1mm so that the screws can slide through easily."}, {"post_id": 646, "ts": "2026-06-02T05:02:32Z", "hours": 0.4175, "text": "I routed the PCB and added some silkscreen designs. I had surprisingly few errors in the DRC, mainly to do with grounding which I fixed by adding vias. I added a rectangle the size of the screen in order to gauge how large it would be. I put the Gerber files into JLCPCB and it would cost 6.60 to produce 5 units, which I think is a pretty alright price. Some issues I faced was that I didn’t realise that my USB port was sticking too far away from the edge until I was about to export the Gerber files and I ended up just cutting the board and rerouting some traces in order to keep it at the edge."}, {"post_id": 628, "ts": "2026-06-02T04:27:25Z", "hours": 2.0125, "text": "1st Jun 9-10PM I worked on making the schematic for my macropad, which I intend to create a mini pet feature. Key features include 4 keys, 1 pushable knob which allows it to switch modes, an OLED screen as well as a status light indicator that changes with the status of the knob."}]...
|
Title: Kittypad by @HY | Stardance
Devlogs:
1st J Title: Kittypad by @HY | Stardance
Devlogs:
1st Jun 9-10PM I worked on making the schematic for my macropad, which I intend to create a mini pet feature. Key features include 4 keys, 1 pushable knob which allows it to switch modes, an OLED screen as well as a status light indicator that changes with the status of the knob.
I routed the PCB and added some silkscreen designs. I had surprisingly few errors in the DRC, mainly to do with grounding which I fixed by adding vias. I added a rectangle the size of the screen in order to gauge how large it would be. I put the Gerber files into JLCPCB and it would cost 6.60 to produce 5 units, which I think is a pretty alright price. Some issues I faced was that I didn’t realise that my USB port was sticking too far away from the edge until I was about to export the Gerber files and I ended up just cutting the board and rerouting some traces in order to keep it at the edge.
Spent a whole bunch of hours fighting Fusion360 to create a base plate. Key features include holes at the bottom in order to put the heat inserts, as well as a drill hole of 3.1mm so that the screws can slide through easily.
I completed the CAD design for the case! I added a counterbore as well as a 3mm thick border around the top case. I left the left side open as part of my design and to show off the silkscreen. I realised that I had used the wrong LED in my PCB and had to face a bunch of DRC errors, because the footprint comes with a hole, the DRC assumed that there was lack of edge clearance and kept giving me the error, so I just ignored the violation.
I created the basic firmware for the Kittypad, I intend to build the ‘game’ after I build the physical macropad so that I am able to test it....
|
1793137967.8965116
|
1793742767.8965116
|
|
1055
|
Micro Speedway by @FabulousHippoOfOrangeLake | Sta Micro Speedway by @FabulousHippoOfOrangeLake | Stardance...
|
FabulousHippoOfOrangeLake
|
1
|
5.0
|
0
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-05T17:06:37Z", "hours": 5.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a traffic navigating game which included npcs of different types Nitro coins gems lives high scores speedometer", "repo": "https://github.com/sharmashashwat27-source/Top_down_endless_racing", "demo": "https://github.com/sharmashashwat27-source/Top_down_endless_racing/releases/tag/pygame"}]...
|
[{"post_id": 77085, "ts": "202 [{"post_id": 77085, "ts": "2026-10-05T16:30:21Z", "hours": 0.7842, "text": "DEVLOG #4 idkk But I made some legendary progress added npcs and a boost mode , this finally bring some structure . I added vibe coded coins and gems btw and in the photo below the car disappears a few moments after the crash and this was the only moment i was able to screenshot after like 8 tries!"}, {"post_id": 74036, "ts": "2026-09-26T16:01:04Z", "hours": 2.0839, "text": "DEVLOG idk but probs the final one… I finished it! its a basic simulation of a highway type setup where u avoid cars and drive accad style nothing very impressive but i/m proud i made this in just 4 hours"}, {"post_id": 53605, "ts": "2026-08-24T07:29:57Z", "hours": 1.9725, "text": "DEVLOG#1 So I started working on this project about a week ago but could only work on it for like a day and a half because of events like HMUN India and stuff. Regardless moving on to to what this project is, Micro Speedway is a top down racing game inspired by old NASCAR arcade games. In the time that i have logged till now I used pygame for the first time in my life and messed around with it to get something close to a car in a circular track, kind of. For me till now everything seems pretty easy to tackle my hardest challenge till now has been using pygame which to be honest wasn’t as hard as I thought it would be and honestly this project is bringing me closer to learn how to properly game design. In the future i look forward to using UNITY to develop a game."}]...
|
Title: Micro Speedway by @FabulousHippoOfOrangeLak Title: Micro Speedway by @FabulousHippoOfOrangeLake | Stardance
Devlogs:
DEVLOG#1 So I started working on this project about a week ago but could only work on it for like a day and a half because of events like HMUN India and stuff. Regardless moving on to to what this project is, Micro Speedway is a top down racing game inspired by old NASCAR arcade games. In the time that i have logged till now I used pygame for the first time in my life and messed around with it to get something close to a car in a circular track, kind of. For me till now everything seems pretty easy to tackle my hardest challenge till now has been using pygame which to be honest wasn’t as hard as I thought it would be and honestly this project is bringing me closer to learn how to properly game design. In the future i look forward to using UNITY to develop a game.
DEVLOG idk but probs the final one… I finished it! its a basic simulation of a highway type setup where u avoid cars and drive accad style nothing very impressive but i/m proud i made this in just 4 hours
DEVLOG #4 idkk But I made some legendary progress added npcs and a boost mode , this finally bring some structure . I added vibe coded coins and gems btw and in the photo below the car disappears a few moments after the crash and this was the only moment i was able to screenshot after like 8 tries!
Ships:
I made a traffic navigating game which included npcs of different types Nitro coins gems lives high scores speedometer...
|
1793152246.3060782
|
1793238646.3060782
|
|
1056
|
Monotony by @Mouse | Stardance
|
Mouse
|
0
|
21.34
|
0
|
[]
|
[{"post_id": 52142, "ts": "202 [{"post_id": 52142, "ts": "2026-08-22T07:19:18Z", "hours": 4.0561, "text": "Performed some shenanigans on the previous versions (naming schemes and broken updates) before deciding to push a new one to follow semantic versioning more strictly. This included renaming the 2nd version from v1.0.1 to v2.0.0 to better signify the overhaul, pushing a new version (v2.1.0, all the updates documented in the last few devlogs), and v2.1.1. This fixed the year-long bug on platform collisions and a gamebreaking bug disabling horizontal movement in v2.1.0, as well as fixing small redundancies in a few classes."}, {"post_id": 47285, "ts": "2026-08-15T04:23:41Z", "hours": 1.1417, "text": "Optimised how levels were drawn by combining the four separate level functions into one (which was put into its own file). This would also prevent exponential scaling in the future seeing how with 4 new game mechanics would result in 64 level functions, creating thousands of unnecessary lines. Furthermore, AI was used to generate a quintic easing function for the mountain lerps, allowing for smoother transitions. In the process, a camera focus bug was also fixed. note: the to-do list is removed since from this point onwards solely new features will be added."}, {"post_id": 45575, "ts": "2026-08-12T04:58:20Z", "hours": 4.0686, "text": "Used AI to mass-anchor the hundreds of game objects automatically, meaning that everything in the game should now dynamically respond to screen size. Updated the about (including the images) and tutorial screens, improved niche applications of syntax and made some small structural changes. The backButton is now fully replaced with the escape key and also applicable in more locations. Several optimisations and changes have been made to titles, subtitles and achievements, including their heights, bounding boxes and dynamic coordinate calculations. Finally, I also improved the transitions in the cursor class to be smoother. To-do: - Remove blurs and symlinks as separate programs - Update extension used - Update README - Create a CHANGELOG.md file - Add compatibility for different screen sizes - Optimisations - Achievements - Tab - Notifications - Blur incorporation as a custom setting - New game mechanics - New levels - Compile and publish a new version"}, {"post_id": 43821, "ts": "2026-08-09T07:58:21Z", "hours": 3.4394, "text": "Fixed a platform collision bug when hitting the side of a platform and improved the implementation of several conventions. Also added support for different screen sizes. Although this hasn’t been implemented with regards to game sprites, it has been done for all other sprites such as menu buttons. To-do: - Remove blurs and symlinks as separate programs - Update extension used - Update README - Create a CHANGELOG.md file - Add compatibility for different screen sizes - Compile and publish a new version - Optimisations - Blur incorporation as a custom setting - Achievements - Tab - Notifications - New game mechanics - New levels note: the image in this devlog is the screen during a failed attempt of adding compatibility."}, {"post_id": 42459, "ts": "2026-08-07T06:37:21Z", "hours": 4.2481, "text": "Published a new version and added a CHANGELOG.md file. I also matched the order of declaration and initialisation, fixed the overlapping coordinates of several achievements, automated the choosing of the next section and fixed another bug related to incorrect fills (caused by the matching of the var dec-init order). To-do: - Remove blurs and symlinks as separate programs - Update extension used - Update README - Create a CHANGELOG.md file - Compile and publish a new version - Optimisations - Blur incorporation as a custom setting - Achievements - Tab - Notifications - New game mechanics - New levels note: the new version bullet point will stay uncrossed until Stardance ends."}, {"post_id": 41730, "ts": "2026-08-06T03:55:18Z", "hours": 2.4969, "text": "Updated the README in terms of formatting and content, which means that now I can start working on the actual game. To-do: - Remove blurs and symlinks as separate programs - Update extension used - Update README - Create a CHANGELOG.md file - Compile and publish a new version - Optimisations - Blur incorporation as a custom setting - Achievements - Tab - Notifications - New game mechanics - New levels"}, {"post_id": 41128, "ts": "2026-08-05T03:56:49Z", "hours": 1.8936, "text": "Removed the need to generate symlinks (replaced by VSCode’s file nesting feature), removed blurs as a separate program (eventually, a customisable seed setting will be added) and switched to Processing’s official extension as opposed to a community-made one."}]...
|
Title: Monotony by @Mouse | Stardance
Devlogs:
Re Title: Monotony by @Mouse | Stardance
Devlogs:
Removed the need to generate symlinks (replaced by VSCode’s file nesting feature), removed blurs as a separate program (eventually, a customisable seed setting will be added) and switched to Processing’s official extension as opposed to a community-made one.
Updated the README in terms of formatting and content, which means that now I can start working on the actual game. To-do: - Remove blurs and symlinks as separate programs - Update extension used - Update README - Create a CHANGELOG.md file - Compile and publish a new version - Optimisations - Blur incorporation as a custom setting - Achievements - Tab - Notifications - New game mechanics - New levels
Published a new version and added a CHANGELOG.md file. I also matched the order of declaration and initialisation, fixed the overlapping coordinates of several achievements, automated the choosing of the next section and fixed another bug related to incorrect fills (caused by the matching of the var dec-init order). To-do: - Remove blurs and symlinks as separate programs - Update extension used - Update README - Create a CHANGELOG.md file - Compile and publish a new version - Optimisations - Blur incorporation as a custom setting - Achievements - Tab - Notifications - New game mechanics - New levels note: the new version bullet point will stay uncrossed until Stardance ends.
Fixed a platform collision bug when hitting the side of a platform and improved the implementation of several conventions. Also added support for different screen sizes. Although this hasn’t been implemented with regards to game sprites, it has been done for all other sprites such as menu buttons. To-do: - Remove blurs and symlinks as separate programs - Update extension used - Update README - Create a CHANGELOG.md file - Add compatibility for different screen sizes - Compile and publish a new version - Optimisations - Blur incorporation as a custom setting - Achievements - Tab - Notifications - New game mechanics - New levels note: the image in this devlog is the screen during a failed attempt of adding compatibility.
Used AI to mass-anchor the hundreds of game objects automatically, meaning that everything in the game should now dynamically respond to screen size. Updated the about (including the images) and tutorial screens, improved niche applications of syntax and made some small structural changes. The backButton is now fully replaced with the escape key and also applicable in more locations. Several optimisations and changes have been made to titles, subtitles and achievements, including their heights, bounding boxes and dynamic coordinate calculations. Finally, I also improved the transitions in the cursor class to be smoother. To-do: - Remove blurs and symlinks as separate programs - Update extension used - Update README - Create a CHANGELOG.md file - Add compatibility for different screen sizes - Optimisations - Achievements - Tab - Notifications - Blur incorporation as a custom setting - New game mechanics - New levels - Compile and publish a new version
Optimised how levels were drawn by combining the four separate level functions into one (which was put into its own file). This would also prevent exponential scaling in the future seeing how with 4 new game mechanics would result in 64 level functions, creating thousands of unnecessary lines. Furthermore, AI was used to generate a quintic easing function for the mountain lerps, allowing for smoother transitions. In the process, a camera focus bug was also fixed. note: the to-do list is removed since from this point onwards solely new features will be added.
Performed some shenanigans on the previous versions (naming schemes and broken updates) before deciding to push a new one to follow semantic versioning more strictly. This included renaming the 2nd version from v1.0.1 to v2.0.0 to better signify the overhaul, pushing a new version (v2.1.0, all the updates documented in the last few devlogs), and v2.1.1. This fixed the year-long bug on platform collisions and a gamebreaking bug disabling horizontal movement in v2.1.0, as well as fixing small redundancies in a few classes....
|
1792673679.295855
|
1793278479.295855
|
|
1057
|
Untitled project by @youtwo_ | Stardance
|
youtwo_
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @youtwo_ | Stardance
|
1792770583.9003766
|
1793375383.9003766
|
|
1058
|
Infinity Orbit Hub by @mohamedsamymohamed | Starda Infinity Orbit Hub by @mohamedsamymohamed | Stardance...
|
mohamedsamymohamed
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Infinity Orbit Hub by @mohamedsamymohamed | Title: Infinity Orbit Hub by @mohamedsamymohamed | Stardance...
|
1793317740.0323029
|
1793922540.0323029
|
|
1059
|
Paradigm by @Dante | Stardance
|
Dante
|
0
|
1.79
|
0
|
[]
|
[{"post_id": 6161, "ts": "2026 [{"post_id": 6161, "ts": "2026-06-10T11:21:59Z", "hours": 0.5728, "text": "Worked on walking animation for player model."}, {"post_id": 4861, "ts": "2026-06-08T12:07:25Z", "hours": 0.7519, "text": "Worked on basic character movement. Next up, going to be working on animations for the character model."}, {"post_id": 3537, "ts": "2026-06-06T14:59:35Z", "hours": 0.4653, "text": "Worked on character modeling. I applied a glowing wireframe to a prexisting character model I created quite a while ago."}]...
|
Title: Paradigm by @Dante | Stardance
Devlogs:
Wo Title: Paradigm by @Dante | Stardance
Devlogs:
Worked on character modeling. I applied a glowing wireframe to a prexisting character model I created quite a while ago.
Worked on basic character movement. Next up, going to be working on animations for the character model.
Worked on walking animation for player model....
|
1792633932.0541742
|
1793238732.0541742
|
|
1060
|
Ball rolling game by @Fatigue34 | Stardance
|
Fatigue34
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Ball rolling game by @Fatigue34 | Stardance
|
1792651757.7824094
|
1793256557.7824094
|
|
1061
|
Hi I'm enshuo, that's my 3D shooting game! Hi I'm enshuo, that's my 3D shooting game! by @En-Shuo | Stardance...
|
En-Shuo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Hi I'm enshuo, that's my 3D shootin Title: Hi I'm enshuo, that's my 3D shooting game! by @En-Shuo | Stardance...
|
1793271251.9536808
|
1793876051.9536808
|
|
1062
|
c by @AboEl5yr | Stardance
|
AboEl5yr
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: c by @AboEl5yr | Stardance
|
1792691273.7611144
|
1793296073.7611144
|
|
1063
|
My awesome macropad! by @Tallini | Stardance
|
Tallini
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Tallini | Stardanc Title: My awesome macropad! by @Tallini | Stardance...
|
1792950502.555547
|
1793814502.555547
|
|
1064
|
🌊Ocean pulse🐢 by @Fai | Stardance
|
Fai
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 🌊Ocean pulse🐢 by @Fai | Stardance
|
1792688025.506578
|
1793292825.506578
|
|
1065
|
TUC by @ciaran | Stardance
|
ciaran
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: TUC by @ciaran | Stardance
|
1793260387.4845743
|
1793865187.4845743
|
|
1066
|
FixHC by @el4s | Stardance
|
el4s
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: FixHC by @el4s | Stardance
|
1792676935.1414845
|
1793281735.1414845
|
|
1067
|
My awesome macropad! by @Himanshu | Stardance
|
Himanshu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Himanshu | Stardan Title: My awesome macropad! by @Himanshu | Stardance...
|
1792911085.2967575
|
1793775085.2967575
|
|
1068
|
ass by @timothy1498 | Stardance
|
timothy1498
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: ass by @timothy1498 | Stardance
|
1793299893.0779696
|
1793904693.0779696
|
|
1069
|
HotBot by @Himanshu | Stardance
|
Himanshu
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: HotBot by @Himanshu | Stardance
|
1792889556.7544408
|
1793753556.7544408
|
|
1070
|
Event Horizon by @notsofastSashmit | Stardance
|
notsofastSashmit
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Event Horizon by @notsofastSashmit | Starda Title: Event Horizon by @notsofastSashmit | Stardance...
|
1793195401.416635
|
1793800201.416635
|
|
1071
|
Test project by @Sahas | Stardance
|
Sahas
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Test project by @Sahas | Stardance
|
1792684163.7727838
|
1793288963.7727838
|
|
1073
|
CYD helper by @Bronson | Stardance
|
Bronson
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: CYD helper by @Bronson | Stardance
|
1792630310.1763244
|
1793235110.1763244
|
|
1074
|
My awesome macropad! by @lillylike123 | Stardance
|
lillylike123
|
0
|
0.72
|
0
|
[]
|
[{"post_id": 9513, "ts": "2026 [{"post_id": 9513, "ts": "2026-06-15T21:39:27Z", "hours": 0.7186, "text": "Worked on the schematic of my first-ever Hackpad (yippee!!!). I am super happy I was able to get the hang of KiCad and its different editors. I hope this Hackpad won’t be my last, and I will make more macro pads for the future!!!"}]...
|
Title: My awesome macropad! by @lillylike123 | Sta Title: My awesome macropad! by @lillylike123 | Stardance
Devlogs:
Worked on the schematic of my first-ever Hackpad (yippee!!!). I am super happy I was able to get the hang of KiCad and its different editors. I hope this Hackpad won’t be my last, and I will make more macro pads for the future!!!...
|
1793253087.342643
|
1793857887.342643
|
|
1075
|
Untitled project by @ARTariqDev | Stardance
|
ARTariqDev
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @ARTariqDev | Stardance
|
1793170170.2807515
|
1793774970.2807515
|
|
1076
|
BAD SPACE UI LAUNCHER by @mrskeleton | Stardance
|
mrskeleton
|
1
|
2.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-02T21:14:45Z", "hours": 2.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Those look like the Stardance project description questions! Here’s what you can put: What did you make? A chaotic pygame game where you try to launch a rocket, but the entire UI is broken and misleading. Sliders are hypersensitive or move backwards, buttons are mislabeled, and a signal bar drifts on its own while you try to hold it steady. What was challenging? Making the controls feel genuinely frustrating without being impossible. Getting the sliders to feel chaotic but still technically winnable took a lot of tweaking. Also setting up Git and GitHub for the first time! What are you proud of? The signal slider that slowly drifts on its own — it makes the game way harder because you have to keep adjusting it while doing everything else at the same time. What should people know to test your project? Install Python and pygame first ( pip install pygame ). Then run rocket_launch.py . To actually launch the rocket: get fuel between 40-60%, pressure between 45-55%, hold the signal between 48-52%, flip both switches ON, press “ABORT MISSION” to arm systems, then press “DO NOT PRESS” to launch. Good luck! 😄", "repo": "https://github.com/I-luvstardance/BAD-SPACE-LAUNCHER-UI", "demo": "https://i-luvstardance.itch.io/bad-space-ui"}]...
|
[{"post_id": 754, "ts": "2026- [{"post_id": 754, "ts": "2026-06-02T12:00:13Z", "hours": 1.7525, "text": "I am working a on a space launcher where the UI is “broken” and you have to try to launch even though. Below is a little bit of my code."}]...
|
Title: BAD SPACE UI LAUNCHER by @mrskeleton | Star Title: BAD SPACE UI LAUNCHER by @mrskeleton | Stardance
Devlogs:
I am working a on a space launcher where the UI is “broken” and you have to try to launch even though. Below is a little bit of my code.
Ships:
Those look like the Stardance project description questions! Here’s what you can put: What did you make? A chaotic pygame game where you try to launch a rocket, but the entire UI is broken and misleading. Sliders are hypersensitive or move backwards, buttons are mislabeled, and a signal bar drifts on its own while you try to hold it steady. What was challenging? Making the controls feel genuinely frustrating without being impossible. Getting the sliders to feel chaotic but still technically winnable took a lot of tweaking. Also setting up Git and GitHub for the first time! What are you proud of? The signal slider that slowly drifts on its own — it makes the game way harder because you have to keep adjusting it while doing everything else at the same time. What should people know to test your project? Install Python and pygame first ( pip install pygame ). Then run rocket_launch.py . To actually launch the rocket: get fuel between 40-60%, pressure between 45-55%, hold the signal between 48-52%, flip both switches ON, press “ABORT MISSION” to arm systems, then press “DO NOT PRESS” to launch. Good luck! 😄...
|
1793267542.5691354
|
1793353942.5691354
|
|
1077
|
My first slack bot! by @pooja235 | Stardance
|
pooja235
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @pooja235 | Stardanc Title: My first slack bot! by @pooja235 | Stardance...
|
1793285541.2057457
|
1793890341.2057457
|
|
1078
|
My first slack bot! by @mazoonelwakeel | Stardance
|
mazoonelwakeel
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @mazoonelwakeel | St Title: My first slack bot! by @mazoonelwakeel | Stardance...
|
1793227739.9375105
|
1793832539.9375105
|
|
1079
|
My first slack bot! by @Aradhana | Stardance
|
Aradhana
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Aradhana | Stardanc Title: My first slack bot! by @Aradhana | Stardance...
|
1792752847.1518354
|
1793357647.1518354
|
|
1080
|
AshBorn by @jean | Stardance
|
jean
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: AshBorn by @jean | Stardance
|
1792691242.8341312
|
1793296042.8341312
|
|
1081
|
My awesome macropad! by @Carbophile | Stardance
|
Carbophile
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Carbophile | Stard Title: My awesome macropad! by @Carbophile | Stardance...
|
1793245890.148067
|
1793850690.148067
|
|
1082
|
Raspberry LED strip by @Levi | Stardance
|
Levi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Raspberry LED strip by @Levi | Stardance
|
1792673266.065377
|
1793278066.065377
|
|
1083
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792943265.4534564
|
1793807265.4534564
|
|
1084
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792936039.4800756
|
1793800039.4800756
|
|
1085
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792936323.3440008
|
1793800323.3440008
|