|
16751
|
Frictionless by @suruthi_s | Stardance
|
suruthi_s
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @suruthi_s | Stardance
|
1793339756.0288115
|
1793944556.0288115
|
|
16752
|
MeowOS! by @CharlieCatMeow | Stardance
|
CharlieCatMeow
|
4
|
55.0
|
668
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-28T16:07:43Z", "hours": 2.0, "multiplier": 18.36, "payout": 35, "blessing": "neutral", "text": "MeowOS! A web based operating system! Built with HTML, CSS, JavaScript and my sanity. I fixed some bugs (you can see them in the last devlog). This is a pretty short ship so don’t expect much to change but yeah. As written in the Devlog, I improved some stuff like the Terminal. Enjoy!", "repo": "https://github.com/CharlieTheCatMeow/WebOS", "demo": "https://charliethecatmeow.github.io/WebOS/"}, {"ship_num": 2, "ts": "2026-08-29T11:29:34Z", "hours": 8.0, "multiplier": 14.98, "payout": 121, "blessing": "neutral", "text": "MeowOS! A web based operating system! Built with HTML, CSS, JavaScript and my sanity. I added a few new features! new themes the browser URL bar now works! yay Added window resizing for most windows. Updated the notes app so the delete button doesn’t remove all pages Added a typing and clicking sound effect (toggle in settings) You can now hide the icon bar when a window is maximized by going into settings. Changed the terminal commands to be more intuitive Fixed a bunch of bugs Also did a bunch of stuff you can’t see to clean up the code, it was pretty messy. (Please read the README as well) Enjoy!", "repo": "https://github.com/CharlieTheCatMeow/WebOS", "demo": "https://charliethecatmeow.github.io/WebOS/"}, {"ship_num": 3, "ts": "2026-07-13T15:29:09Z", "hours": 33.0, "multiplier": 15.49, "payout": 512, "blessing": "neutral", "text": "✨ MeowOS! ✨ MeowOS! is a web based operating system built to enhance productivity with a wide range of apps to be used. It is built on HTML, CSS and Javascript. ✨Apps✨: Introduction (a guide to the website) Stopwatch (Keep track of how much time has past) Notes (Write down your thoughts To-do list (write down tasks and procrastinate) Calculator (do math - scary) Music Player (play some music) Gallery (view images) Browser (browser through three webpages) File explorer (create .txt files and folders) Settings (configure stuff like Widgets and more) Terminal (run commands) ✨Other Features✨: Search menu (to search for apps) Control center (controls brightness, volume and connectivity) Cat widget (click to meow) Calendar (view today’s date) Minimalist Clock (read the time) Dark / Light mode (toggle in settings) Loading screen This is my first time creating a website. Doing WebOS 1 really helped me get a grasp of the basics. I was a total beginner at this and yet more than 10 Devlogs later here I am. As you can probably tell by the amount of hours on this project, it wasn’t all sunshine and rainbows. Maximizing and moving windows was the things I struggled most with. It took me way too long to fix the millions of bugs associated with window dragging, maximizing and positioning. The website turned out better than I could have ever imagined and I hope you enjoy using it. I am particularly proud of the dark mode (find in settings), I think it looks amazing. Enough yap, enjoy the website :3 (if the blur effect doesn’t work please skip this project, thank you!)", "repo": "https://github.com/CharlieTheCatMeow/WebOS", "demo": "https://charliethecatmeow.github.io/WebOS/"}, {"ship_num": 4, "ts": "2026-07-04T09:53:06Z", "hours": 12.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "My very own web-based operating system! It features: Notes App (you can add pages) Stopwatch To-Do List Clock Took me a while to figure out. Javascript was the hardest for me since I’ve only ever coded in Python, but I managed. Hope this gets approved so I can continue working on it (with more stardust :D)", "repo": "https://github.com/CharlieTheCatMeow/WebOS", "demo": "https://charliethecatmeow.github.io/WebOS/"}]...
|
[{"post_id": 83775, "ts": "202 [{"post_id": 83775, "ts": "2026-10-28T16:04:27Z", "hours": 1.9056, "text": "MeowOS Devlog #16 Bug fixes (a lot) With the help of a totally trustworthy AI, I found a bunch of edge cases, bugs and typos. Also added some stuff So I fixed them one by one over the course of 2 hours (and also updated the README and added some small stuff). Some of the bugs I found and fixed: Mistyped the volume muted icon Sound effect weren’t applied the audio level Some stuff I added: Opening browser shortcuts now uses the dedicated function instead of plain HTML Terminal now works better Keyboard support for Calculator"}, {"post_id": 57257, "ts": "2026-08-29T11:20:43Z", "hours": 0.5786, "text": "MeowOS Devlog #15 Some small changes before shipping! Made the clicking and typing sound be turned on by default Changed some window width settings Changed terminal commands a bit Fixed the search menu icon size I should be able to ship this now."}, {"post_id": 54595, "ts": "2026-08-25T16:54:45Z", "hours": 1.1153, "text": "MeowOS Devlog #14 Added a pink theme This was upon request by someone from slack, they wanted a pink theme so here it is. Changes to the terminal I reworked some commands. I bundled all the app commands into one, so it’s no longer “todo”, but “app todo”. It’s a bit cleaner. Also did this with the themes, but I forgot if I did it this devlog or the last one. Setting for maximizing window There is now an option in the settings to hide the taskbar (the thing on the bottom) when the window is maximized. I really over complicated things while trying to make it work, found out it was just a one single line of code that was needed. This should be all I think"}, {"post_id": 53227, "ts": "2026-08-23T17:47:34Z", "hours": 3.9083, "text": "MeowOS Devlog #13 Themes! I decided do a complete overhaul of the themes. Instead of dark and light mode, there are no five different themes to choose from. I had to refactor almost everything since the code from before was pretty poorly made. Browser URL bar The browser URL bar works now! You can now enter website addresses and they should show up. (Do note that some websites block iframes and may not work). Some sound effects I added a typing and clicking sound effect. You need to enable it in settings. Small tweaks I finally changed the notes delete button. Instead of deleting every page, it now only deletes the current one. Also, the placeholders are actual placeholders now, so they hide themselves when selecting the text and reappear if the text is left empty. The title and date of the notes also get saved now. I found out why the music player playlist wasn’t getting resized along with the window, I was able to fix it with just one line of CSS code. Fixed the stopwatch reset button not changing the play button’s icon if the time was still running."}, {"post_id": 52885, "ts": "2026-08-23T08:22:56Z", "hours": 2.4619, "text": "MeowOS Devlog #12 Some small stuff Resizable windows! I made most windows resizable. I had to fix a lot of CSS for that, but I’m glad it works now. Also tweaked some minor stuff. (Notice how windows are smaller in the picture)"}, {"post_id": 27712, "ts": "2026-07-13T14:38:25Z", "hours": 3.7478, "text": "MeosOS Devlog #11 More bug fixes and also widgets!!! I did some more bug fixing with the dark and light mode as well as window scaling. I think all bugs should be gone now, though I’m not entirely sure I didn’t miss any. Widgets I added three widgets: cat you can click to meow calendar a minimalist round clock That’s all. I hope I can ship this now. (Though I am a bit paranoid of issues I didn’t notice)"}, {"post_id": 27330, "ts": "2026-07-12T20:18:07Z", "hours": 4.935, "text": "MeowOS Devlog #10 Bug fixes and control center Not much to say about this one. I spent a long time fixing a bunch of bugs and polishing the website. I also added a control center to the top right. I gotta find some creative ideas to add to this hmm…"}, {"post_id": 27128, "ts": "2026-07-12T12:30:37Z", "hours": 5.335, "text": "MeowOS Devlog #9 File explorer! This was by far the hardest window to implement. Took me quite a while to figure out the recursive functions to browse through the files. Features: Create folders Create text files Write things in text files Delete files and folders Everything is saved to localStorage This was very fun. Javascript got kind of difficult but it turned out great. I will probably create some widgets now. :D"}, {"post_id": 26605, "ts": "2026-07-11T15:09:33Z", "hours": 7.01, "text": "MeowOS Devlog #8 Another kinda long one…I got a bit carried away. Maximize windows I finally added a function to maximize certain windows. There were way too many bugs associated with that feature, that took way too long. Especially hiding the top bar while a window is maximized. Loading screen I also made the loading screen stay a bit longer on screen so people with high internet speeds will still be able to see it. Gallery Probably the easiest task of this devlog. Not much to say about it, it’s a gallery with pictures. Search menu This one worked surprisingly well. I somehow got the search function right in the first two attempts. Very fun to make. Light / Dark mode I changed my mind. This was the easiest task. I was avoiding this since I thought it would be super complicated, but it turns out it’s not. :D That’s all I did. I still have a few apps in mind, so I’ll start working on those soon."}, {"post_id": 25876, "ts": "2026-07-10T11:19:21Z", "hours": 2.6578, "text": "MeowOS Devlog #7 Music App I finally finished the music application. I still have to find some songs I am allowed to put in there. Loading Screen I also added a loading screen with a cat-shaped loading bar. Took me a while to figure out how an svg works. The text also has an animation to make it more interesting. Easter egg I added an easter egg. It’s not much and not that difficult to find, but I won’t reveal what it is. That’s all :D"}, {"post_id": 25349, "ts": "2026-07-09T16:10:03Z", "hours": 9.3508, "text": "MeowOS Devlog #6 It’s a long one… Since I finally got my ship approved, I can now post my 9 hour devlog D: I added a bunch of things and improved the design by a lot: New Design, looks much prettier Animations for interactive elements A command terminal, you can open windows with it A calculator, to calculate stuff ;-; a WIP music player (I need to find songs) A start menu before loading the OS. Took me quite a while to figure out. Javascript isn’t really a problem anymore. I really enjoyed updating the design in CSS using :hover and keyframes. I’m very happy of how it all turned out."}, {"post_id": 22068, "ts": "2026-07-04T09:50:36Z", "hours": 1.0447, "text": "MeowOS Devlog #5 I fixed some bugs. I didn’t do too much. It is now time to ship this project. I hope that it works!"}, {"post_id": 21429, "ts": "2026-07-03T11:40:25Z", "hours": 3.8028, "text": "MeowOS Devlog #4 Getting the hang of Javascript I made my own Stopwatch app without following the guide. Took me a while but I completed it and I am very happy with the result. I am now trying to do some more complex apps before shipping this project. I still have some work to do, as the To-Do List App is not finished and a terminal App is missing. That’s all .D"}, {"post_id": 18362, "ts": "2026-06-29T14:23:32Z", "hours": 3.1842, "text": "MeowOS Devlog #3 Still learning Javascript Javascript is still kind of confusing for me, I’m starting to figure it out though. Notes App I finished my first app with functionality. You can write stuff in it. Unlimited new note pages can also be created and there is a button to wipe everything. Looking forward to adding additional content :D"}, {"post_id": 13723, "ts": "2026-06-22T14:30:16Z", "hours": 2.6383, "text": "MeowOS Devlog #2 Learning Javascript Javascript took me a while to figure out. I found getting the Javascript file to work with the website a bit confusing, but the guide helped me through it. I have added: App icons (though not all of them assigned) two apps (still empty) draggable close / open them the selected app sits on top. I look forward to coding my first proper app with functions. That’s all :D"}, {"post_id": 12458, "ts": "2026-06-20T10:47:00Z", "hours": 1.6758, "text": "MeowOS (placeholder name) My first html project! I had some prior basic html knowledge, but that was a long time ago. I chose this mission because: I want to improve my website development skills This mission gives practically infinite possibilities for apps, so I have a lot of creative freedom With the first 100 minutes now logged, this is what I completed: a desktop background a top bar a clock a temporary non-draggable window I’m trying to not use pixels as measurement since I want the website to work on all resolutions. I’ll see if that will work out. All in all, I’m very happy with the design. I got back into html and didn’t feel like anything was that challenging yet. I have never done Javascript though, that will probably be a bit harder."}]...
|
Title: MeowOS! by @CharlieCatMeow | Stardance
Dev Title: MeowOS! by @CharlieCatMeow | Stardance
Devlogs:
MeowOS (placeholder name) My first html project! I had some prior basic html knowledge, but that was a long time ago. I chose this mission because: I want to improve my website development skills This mission gives practically infinite possibilities for apps, so I have a lot of creative freedom With the first 100 minutes now logged, this is what I completed: a desktop background a top bar a clock a temporary non-draggable window I’m trying to not use pixels as measurement since I want the website to work on all resolutions. I’ll see if that will work out. All in all, I’m very happy with the design. I got back into html and didn’t feel like anything was that challenging yet. I have never done Javascript though, that will probably be a bit harder.
MeowOS Devlog #2 Learning Javascript Javascript took me a while to figure out. I found getting the Javascript file to work with the website a bit confusing, but the guide helped me through it. I have added: App icons (though not all of them assigned) two apps (still empty) draggable close / open them the selected app sits on top. I look forward to coding my first proper app with functions. That’s all :D
MeowOS Devlog #3 Still learning Javascript Javascript is still kind of confusing for me, I’m starting to figure it out though. Notes App I finished my first app with functionality. You can write stuff in it. Unlimited new note pages can also be created and there is a button to wipe everything. Looking forward to adding additional content :D
MeowOS Devlog #4 Getting the hang of Javascript I made my own Stopwatch app without following the guide. Took me a while but I completed it and I am very happy with the result. I am now trying to do some more complex apps before shipping this project. I still have some work to do, as the To-Do List App is not finished and a terminal App is missing. That’s all .D
MeowOS Devlog #5 I fixed some bugs. I didn’t do too much. It is now time to ship this project. I hope that it works!
MeowOS Devlog #6 It’s a long one… Since I finally got my ship approved, I can now post my 9 hour devlog D: I added a bunch of things and improved the design by a lot: New Design, looks much prettier Animations for interactive elements A command terminal, you can open windows with it A calculator, to calculate stuff ;-; a WIP music player (I need to find songs) A start menu before loading the OS. Took me quite a while to figure out. Javascript isn’t really a problem anymore. I really enjoyed updating the design in CSS using :hover and keyframes. I’m very happy of how it all turned out.
MeowOS Devlog #7 Music App I finally finished the music application. I still have to find some songs I am allowed to put in there. Loading Screen I also added a loading screen with a cat-shaped loading bar. Took me a while to figure out how an svg works. The text also has an animation to make it more interesting. Easter egg I added an easter egg. It’s not much and not that difficult to find, but I won’t reveal what it is. That’s all :D
MeowOS Devlog #8 Another kinda long one…I got a bit carried away. Maximize windows I finally added a function to maximize certain windows. There were way too many bugs associated with that feature, that took way too long. Especially hiding the top bar while a window is maximized. Loading screen I also made the loading screen stay a bit longer on screen so people with high internet speeds will still be able to see it. Gallery Probably the easiest task of this devlog. Not much to say about it, it’s a gallery with pictures. Search menu This one worked surprisingly well. I somehow got the search function right in the first two attempts. Very fun to make. Light / Dark mode I changed my mind. This was the easiest task. I was avoiding this since I thought it would be super complicated, but it turns out it’s not. :D That’s all I did. I still have a few apps in mind, so I’ll start working on those soon.
MeowOS Devlog #9 File explorer! This was by far the hardest window to implement. Took me quite a while to figure out the recursive functions to browse through the files. Features: Create folders Create text files Write things in text files Delete files and folders Everything is saved to localStorage This was very fun. Javascript got kind of difficult but it turned out great. I will probably create some widgets now. :D
MeowOS Devlog #10 Bug fixes and control center Not much to say about this one. I spent a long time fixing a bunch of bugs and polishing the website. I also added a control center to the top right. I gotta find some creative ideas to add to this hmm…
MeosOS Devlog #11 More bug fixes and also widgets!!! I did some more bug fixing with the dark and light mode as well as window scaling. I think all bugs should be gone now, though I’m not entirely sure I didn’t miss any. Widgets I added three widgets: cat you can click to meow calendar a minimalist round clock That’s all. I hope I can ship this now. (Though I am a bit paranoid of issues I didn’t notice)
MeowOS Devlog #12 Some small stuff Resizable windows! I made most windows resizable. I had to fix a lot of CSS for that, but I’m glad it works now. Also tweaked some minor stuff. (Notice how windows are smaller in the picture)
MeowOS Devlog #13 Themes! I decided do a complete overhaul of the themes. Instead of dark and light mode, there are no five different themes to choose from. I had to refactor almost everything since the code from before was pretty poorly made. Browser URL bar The browser URL bar works now! You can now enter website addresses and they should show up. (Do note that some websites block iframes and may not work). Some sound effects I added a typing and clicking sound effect. You need to enable it in settings. Small tweaks I finally changed the notes delete button. Instead of deleting every page, it now only deletes the current one. Also, the placeholders are actual placeholders now, so they hide themselves when selecting the text and reappear if the text is left empty. The title and date of the notes also get saved now. I found out why the music player playlist wasn’t getting resized along with the window, I was able to fix it with just one line of CSS code. Fixed the stopwatch reset button not changing the play button’s icon if the time was still running.
MeowOS Devlog #14 Added a pink theme This was upon request by someone from slack, they wanted a pink theme so here it is. Changes to the terminal I reworked some commands. I bundled all the app commands into one, so it’s no longer “todo”, but “app todo”. It’s a bit cleaner. Also did this with the themes, but I forgot if I did it this devlog or the last one. Setting for maximizing window There is now an option in the settings to hide the taskbar (the thing on the bottom) when the window is maximized. I really over complicated things while trying to make it work, found out it was just a one single line of code that was needed. This should be all I think
MeowOS Devlog #15 Some small changes before shipping! Made the clicking and typing sound be turned on by default Changed some window width settings Changed terminal commands a bit Fixed the search menu icon size I should be able to ship this now.
MeowOS Devlog #16 Bug fixes (a lot) With the help of a totally trustworthy AI, I found a bunch of edge cases, bugs and typos. Also added some stuff So I fixed them one by one over the course of 2 hours (and also updated the README and added some small stuff). Some of the bugs I found and fixed: Mistyped the volume muted icon Sound effect weren’t applied the audio level Some stuff I added: Opening browser shortcuts now uses the dedicated function instead of plain HTML Terminal now works better Keyboard support for Calculator
Ships:
My very own web-based operating system! It features: Notes App (you can add pages) Stopwatch To-Do List Clock Took me a while to figure out. Javascript was the hardest for me since I’ve only ever coded in Python, but I managed. Hope this gets approved so I can continue working on it (with more stardust :D)
✨ MeowOS! ✨ MeowOS! is a web based operating system built to enhance productivity with a wide range of apps to be used. It is built on HTML, CSS and Javascript. ✨Apps✨: Introduction (a guide to the website) Stopwatch (Keep track of how much time has past) Notes (Write down your thoughts To-do list (write down tasks and procrastinate) Calculator (do math - scary) Music Player (play some music) Gallery (view images) Browser (browser through three webpages) File explorer (create .txt files and folders) Settings (configure stuff like Widgets and more) Terminal (run commands) ✨Other Features✨: Search menu (to search for apps) Control center (controls brightness, volume and connectivity) Cat widget (click to meow) Calendar (view today’s date) Minimalist Clock (read the time) Dark / Light mode (toggle in settings) Loading screen This is my first time creating a website. Doing WebOS 1 really helped me get a grasp of the basics. I was a total beginner at this and yet more than 10 Devlogs later here I am. As you can probably tell by the amount of hours on this project, it wasn’t all sunshine and rainbows. Maximizing and moving windows was the things I struggled most with. It took me way too long to fix the millions of bugs associated with window dragging, maximizing and positioning. The website turned out better than I could have ever imagined and I hope you enjoy using it. I am particularly proud of the dark mode (find in settings), I think it looks amazing. Enough yap, enjoy the website :3 (if the blur effect doesn’t work please skip this project, thank you!)
MeowOS! A web based operating system! Built with HTML, CSS, JavaScript and my sanity. I added a few new features! new themes the browser URL bar now works! yay Added window resizing for most windows. Updated the notes app so the delete button doesn’t remove all pages Added a typing and clicking sound effect (toggle in settings) You can now hide the icon bar when a window is maximized by going into settings. Changed the terminal commands to be more intuitive Fixed a bunch of bugs Also did a bunch of stuff you can’t see to clean up the code, it was pretty messy. (Please read the README as well) Enjoy!
MeowOS! A web based operating system! Built with HTML, CSS, JavaScript and my sanity. I fixed some bugs (you can see them in the last devlog). This is a pretty short ship so don’t expect much to change but yeah. As written in the Devlog, I improved some stuff like the Terminal. Enjoy!...
|
1793681620.1532097
|
1793768020.1532097
|
|
16753
|
Flower game by @Alafandri | Stardance
|
Alafandri
|
1
|
4.0
|
17
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-23T15:05:54Z", "hours": 4.0, "multiplier": 4.1, "payout": 17, "blessing": "neutral", "text": "I made a godot game to improve myself in using godot and getting more familiar with its programming language. Challenging was keeping the motivation. When you are hit with a problem suddnely out of nowhere then it can be so annoying tracking down the cause of the problem. I am proud of the art. I think i did very well with it. When people test out my project they should know that it’s not much but I still spent a lot of time trying my best to make it so I hope you enjoy!", "repo": "https://github.com/Alafandri/StardanceProject", "demo": "https://alafandri.itch.io/flower-game"}]...
|
[{"post_id": 11568, "ts": "202 [{"post_id": 11568, "ts": "2026-06-18T21:07:00Z", "hours": 0.7981, "text": "Devlog #4 Hello everyone, this is the fourth devlog! Everything new: Goal Timer Main menu A way to win Victory screen So basically the biggest thing I have added this time is that this game is now actually winnable. Obviously this isn’t and won’t be the final version for the game but the main core systems are in place now. That means that I can now start working on other things like adding some visual effects and polishing the game out even more. I feel like this isn’t enough for the game so I absolutely want to expand on this game. So next time you can hope for more polished version of the game. And I will also be starting to sort everything because stuff are pretty messy currently. That is it for today so see you next time!"}, {"post_id": 10936, "ts": "2026-06-17T22:31:10Z", "hours": 1.1256, "text": "Devlog #3 Hello everyone once again! Back here with the third devlog!!! This one adds quite a few things. Everything new: Gave everything an actual function(meaning that the tools can actually do something now) Lives End screen It’s a very simple game but I got big plans for it(which I will keep as a secret for now) and so far I have been having so much fun making it. Just making something yourself and feeling productive instead of rotting in bed all day watching youtube feels so nice. The people who have commented or like my posts thank you so much cause yall are so nice and just the best. I love the feeling when I have made some actual changes to the game and then I go to github desktop to push all the changes and I can see everything that is about to be committed to github it just feels so satisfying. This keeps me going and I really hope that this post might motivate someone to work on their project cause yall projects motivate me. You guys got so much passion and are just so talented that I just love so much. Anyways I got a little distracted so let’s continue talking about the changes to the game. So as you might have read from everything new then everything has a function now finally. There is finally some gameplay, yay. But yeah, I made the tools movable already in the last devlog so that’s been a thing in the game already but they actually didn’t do anything before but now I have made a little randomized system where the flower picks a random thing that it wants and displays it on the text label. If you give the correct thing then nothing happens but if you give the wrong thing then you lose a live. It’s a pretty simple system. And obviously if you run out of lives then everything will be turned invisible and the end screen appears. Planned next: a timer goal start screen make it more satisfying But that is it for this devlog! See you next time. Byeeee. :)"}, {"post_id": 10244, "ts": "2026-06-16T21:33:28Z", "hours": 1.0611, "text": "Devlog #2 Hey everyone! The second devlog for my godot game is finally here! I have done several new things: Drag and drop system Drawn some sprites Written some lore(I like my games with lore, it helps me guide) Basic gameplay loop idea Probably the biggest thing currently is the drag and drop system. Even though not complex at all then still very important feature for the game. The drag and drop system is important cause the whole game will be relying on it and I wanted for it to feel nice. I am definitely planning on expanding on it to make it feel more satisfying(I have some ideas). I think that it’s very important for your games to feel nice or i guess in other words ‘satisfying’ and obviously they should be fun. So my game idea to make something like the game Mr.TomatoS . I’ve always like the idea behind the game and especially the lore and I have always wanted to make something like this. This game is mostly for me to get better at development and just to have fun while making it. If the dev has fun making the game then the better the game will end up. Now I think we have talked enough about the drag and drop system so let’s talk about the sprites. To me is always very important to make a atmosphere for your game which tells you all you need to know about the game and I think it should give you a glimpse of whats about to happen without really telling you in words. So that’s why the sprites and visual effects are very important. Currently I have worked on at all on the visual side cause that I should work on more when I am polishing the game. But I still wanted to game to look better when testing cause I have gotten tired of staring these godot cubes. So that’s why I have some basic most important sprites in the game. Also I would like to say that these sprites are probably not final and they might be changed. Anyways enough of yapping and time to get back developing. Have a nice day!!! :)"}, {"post_id": 9872, "ts": "2026-06-16T10:26:58Z", "hours": 1.1692, "text": "Devlog #1 ㅤ I have created the godot game project and started developing my game. I already have some ideas for the game too which I won’t be talking too much about in this devlog but all you need to know is that it will be a pretty basic 2D game and that it won’t be a platformer. What I’m trying to achieve with this project is to get better in game development and by that I mean coding, game design and etc… All I’ve made currently is just a little textbox(which I will probably end up removing) where you can enter your name and move on to the actual game. I don’t have much anything else to talk about so see you soon in the next devlog!"}]...
|
Title: Flower game by @Alafandri | Stardance
Devl Title: Flower game by @Alafandri | Stardance
Devlogs:
Devlog #1 ㅤ I have created the godot game project and started developing my game. I already have some ideas for the game too which I won’t be talking too much about in this devlog but all you need to know is that it will be a pretty basic 2D game and that it won’t be a platformer. What I’m trying to achieve with this project is to get better in game development and by that I mean coding, game design and etc… All I’ve made currently is just a little textbox(which I will probably end up removing) where you can enter your name and move on to the actual game. I don’t have much anything else to talk about so see you soon in the next devlog!
Devlog #2 Hey everyone! The second devlog for my godot game is finally here! I have done several new things: Drag and drop system Drawn some sprites Written some lore(I like my games with lore, it helps me guide) Basic gameplay loop idea Probably the biggest thing currently is the drag and drop system. Even though not complex at all then still very important feature for the game. The drag and drop system is important cause the whole game will be relying on it and I wanted for it to feel nice. I am definitely planning on expanding on it to make it feel more satisfying(I have some ideas). I think that it’s very important for your games to feel nice or i guess in other words ‘satisfying’ and obviously they should be fun. So my game idea to make something like the game Mr.TomatoS . I’ve always like the idea behind the game and especially the lore and I have always wanted to make something like this. This game is mostly for me to get better at development and just to have fun while making it. If the dev has fun making the game then the better the game will end up. Now I think we have talked enough about the drag and drop system so let’s talk about the sprites. To me is always very important to make a atmosphere for your game which tells you all you need to know about the game and I think it should give you a glimpse of whats about to happen without really telling you in words. So that’s why the sprites and visual effects are very important. Currently I have worked on at all on the visual side cause that I should work on more when I am polishing the game. But I still wanted to game to look better when testing cause I have gotten tired of staring these godot cubes. So that’s why I have some basic most important sprites in the game. Also I would like to say that these sprites are probably not final and they might be changed. Anyways enough of yapping and time to get back developing. Have a nice day!!! :)
Devlog #3 Hello everyone once again! Back here with the third devlog!!! This one adds quite a few things. Everything new: Gave everything an actual function(meaning that the tools can actually do something now) Lives End screen It’s a very simple game but I got big plans for it(which I will keep as a secret for now) and so far I have been having so much fun making it. Just making something yourself and feeling productive instead of rotting in bed all day watching youtube feels so nice. The people who have commented or like my posts thank you so much cause yall are so nice and just the best. I love the feeling when I have made some actual changes to the game and then I go to github desktop to push all the changes and I can see everything that is about to be committed to github it just feels so satisfying. This keeps me going and I really hope that this post might motivate someone to work on their project cause yall projects motivate me. You guys got so much passion and are just so talented that I just love so much. Anyways I got a little distracted so let’s continue talking about the changes to the game. So as you might have read from everything new then everything has a function now finally. There is finally some gameplay, yay. But yeah, I made the tools movable already in the last devlog so that’s been a thing in the game already but they actually didn’t do anything before but now I have made a little randomized system where the flower picks a random thing that it wants and displays it on the text label. If you give the correct thing then nothing happens but if you give the wrong thing then you lose a live. It’s a pretty simple system. And obviously if you run out of lives then everything will be turned invisible and the end screen appears. Planned next: a timer goal start screen make it more satisfying But that is it for this devlog! See you next time. Byeeee. :)
Devlog #4 Hello everyone, this is the fourth devlog! Everything new: Goal Timer Main menu A way to win Victory screen So basically the biggest thing I have added this time is that this game is now actually winnable. Obviously this isn’t and won’t be the final version for the game but the main core systems are in place now. That means that I can now start working on other things like adding some visual effects and polishing the game out even more. I feel like this isn’t enough for the game so I absolutely want to expand on this game. So next time you can hope for more polished version of the game. And I will also be starting to sort everything because stuff are pretty messy currently. That is it for today so see you next time!
Ships:
I made a godot game to improve myself in using godot and getting more familiar with its programming language. Challenging was keeping the motivation. When you are hit with a problem suddnely out of nowhere then it can be so annoying tracking down the cause of the problem. I am proud of the art. I think i did very well with it. When people test out my project they should know that it’s not much but I still spent a lot of time trying my best to make it so I hope you enjoy!...
|
1793789707.969838
|
1793876107.969838
|
|
16754
|
My first slack bot! by @Mariah-Evelyn | Stardance
|
Mariah-Evelyn
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Mariah-Evelyn | Sta Title: My first slack bot! by @Mariah-Evelyn | Stardance...
|
1793569948.7715788
|
1794174748.7715788
|
|
16755
|
Automatic Window by @JoshuaGupta-Pontius | Stardan Automatic Window by @JoshuaGupta-Pontius | Stardance...
|
JoshuaGupta-Pontius
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Automatic Window by @JoshuaGupta-Pontius | Title: Automatic Window by @JoshuaGupta-Pontius | Stardance...
|
1793310770.4492521
|
1793915570.4492521
|
|
16756
|
My awesome macropad! by @Domenix | Stardance
|
Domenix
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Domenix | Stardanc Title: My awesome macropad! by @Domenix | Stardance...
|
1793220716.1989117
|
1793825516.1989117
|
|
16757
|
Frictionless by @arjunkhedkar | Stardance
|
arjunkhedkar
|
0
|
1.34
|
0
|
[]
|
[{"post_id": 7042, "ts": "2026 [{"post_id": 7042, "ts": "2026-06-11T20:05:31Z", "hours": 1.3428, "text": "Created the first prototype. Uses GraphHopper for the backend, which is hosted locally on a Raspberry Pi, and the web app creates the routes. Need to figure out how to send to Garmin as that feature does not work yet."}]...
|
Title: Frictionless by @arjunkhedkar | Stardance
Title: Frictionless by @arjunkhedkar | Stardance
Devlogs:
Created the first prototype. Uses GraphHopper for the backend, which is hosted locally on a Raspberry Pi, and the web app creates the routes. Need to figure out how to send to Garmin as that feature does not work yet....
|
1793368230.9085777
|
1793973030.9085777
|
|
16758
|
My first slack bot! by @Tarannum | Stardance
|
Tarannum
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Tarannum | Stardanc Title: My first slack bot! by @Tarannum | Stardance...
|
1793573356.0838215
|
1794178156.0838215
|
|
16759
|
My first slack bot! by @adji3 | Stardance
|
adji3
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @adji3 | Stardance
|
1793444160.8037407
|
1794048960.8037407
|
|
16760
|
Charie by @Electric_angel | Stardance
|
Electric_angel
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Charie by @Electric_angel | Stardance
|
1793401037.6434617
|
1794005837.6434617
|
|
16761
|
Frictionless by @varia | Stardance
|
varia
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @varia | Stardance
|
1793415409.1582046
|
1794020209.1582046
|
|
16762
|
Frictionless by @sharpjohnathan | Stardance
|
sharpjohnathan
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @sharpjohnathan | Stardance
|
1793407733.0004141
|
1794012533.0004141
|
|
16763
|
My very own WebOS by @Kashviii | Stardance
|
Kashviii
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Kashviii | Stardance
|
1793332073.3401742
|
1793936873.3401742
|
|
16764
|
My very own WebOS by @Sherlocktones | Stardance
|
Sherlocktones
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Sherlocktones | Stard Title: My very own WebOS by @Sherlocktones | Stardance...
|
1793469235.7050402
|
1794074035.7050402
|
|
16765
|
mental-health check website by @Cass | Stardance
|
Cass
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: mental-health check website by @Cass | Star Title: mental-health check website by @Cass | Stardance...
|
1793508694.2669737
|
1794113494.2669737
|
|
16766
|
My first slack bot! by @willowbellows | Stardance
|
willowbellows
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @willowbellows | Sta Title: My first slack bot! by @willowbellows | Stardance...
|
1793300172.0337822
|
1793904972.0337822
|
|
16767
|
My very own WebOS by @Cloud4D | Stardance
|
Cloud4D
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Cloud4D | Stardance
|
1793166569.422885
|
1793771369.422885
|
|
16768
|
Ellery AI by @Ishaan_Jha | Stardance
|
Ishaan_Jha
|
1
|
27.0
|
0
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-29T04:55:09Z", "hours": 27.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "Ellery is being shipped. I spent the last stretch cleaning up the codebase, removing unused features, tightening the documentation, and making the reasoning behind each finding easier to verify. The goal was never just to make charts. It’s to help people understand what their data actually says, and trace every conclusion back to its evidence. The goal is to simplify the messy data.", "repo": "https://github.com/IJai-code/storydata-ai", "demo": "https://ijai-code.github.io/storydata-ai/"}]...
|
[{"post_id": 72498, "ts": "202 [{"post_id": 72498, "ts": "2026-09-23T02:34:51Z", "hours": 2.2061, "text": "Cleaned up the site, fixed some very minor bugs, but the core of the site is set in stone. As stardance wraps up I want to make final minor tweaks, let claude scan through to find any bugs (dw i am under 30 percent ai, i just spent more than 30 percent of time on it with ai, but the code itself is def written more by me.) ready to ship soon –– also kept a changelog, so it has its own mini devlog list within. btw it will prob be in early access when shipped because i dont think it is at the level where it is worthy of a cost/payment, not even close, but it isn’t a bad app itself… i hope :)"}, {"post_id": 41175, "ts": "2026-08-05T06:40:12Z", "hours": 7.5186, "text": "Devlog - how I accidentally almost shipped a lie detector that couldn’t detect lies: So Ellery already told you what was true about your data. Findings, plain English, click one and it peels open down to the exact rows. Nice. The problem was how it did that.Every finding carried a loose bag of numbers called evidence. And then, three separate times, a file called pull.js squinted at that bag and tried to reverse-engineer what the detector had been thinking. Three parallel switch (detector) statements. One to figure out which rows mattered, one to write the explanation sentence, one to write the derivation. Add a detector, edit four files, pray. Worst part: to figure out which rows a finding covered, pull.js re-ran the detector’s filter from scratch. Two copies of the same logic, living in different files, free to disagree. The finding says “3 records are low on stock,” the highlight lights up 4, and nobody notices for six months.The fix, and the part where I was wrongReplace the bag of numbers with an actual graph. Each finding now carries the computation that made it - max over a column, count over classified statuses - as nodes that hash to their own content, bottoming out at fingerprinted cells.I’d designed the graph nodes to include their computed value in their identity. Claude pushed back: separate identity from evaluation. The node names the computation; the value is what you get when you run it against data. Fine, sure, whatever - except it turns out that’s the entire ballgame, because now you get two fingerprints. One for the reasoning, one for the reasoning-applied-to-this-data. Which means the app can now tell you “your numbers changed but the logic didn’t” versus “the logic itself moved.” That’s a genuinely different product capability and it fell out of a definition change.Second thing I got wrong: I’d let the graph carry rowIndices. Row indices! In the evidence layer! That’s render state wearing a trenchcoat. Now it carries a witness - records addressed by content fingerprint - and the renderer figures out where they currently sit. Also, a haunting: Spent a solid while convinced the trace had 1,200px of unreachable content. Built a control experiment. Scrolling was fine. The real culprit was scroll-behavior: smooth - I was setting the scroll position and reading it back mid-animation, watching it clamp at 61.5px, and concluding the layout was broken. There was no bug. I nearly “fixed” a phantom. Small indignity: While all this was happening we discovered npm run lint was pointed at public/js, a directory that hasn’t existed since the frontend moved to the repo root. It had been linting nothing. For a while. Repointed it, and it immediately snitched on a pile of dead imports. Shipped: the derivation graph, two-fingerprint identity, a verify button that can actually say no, golden tests over the whole truth path, and a linter that lints. Deleted: more than I added, where it counted."}, {"post_id": 31658, "ts": "2026-07-20T07:33:01Z", "hours": 5.3633, "text": "Devlog #3 - Making the app more open and dynamic: I am working on making the app feel less claustrophobic, adding/updating engines like the research engine, and making the UI more professional and multipage. Not commited and running yet, but almost there."}, {"post_id": 24484, "ts": "2026-07-08T01:49:29Z", "hours": 3.9758, "text": "Ellery Devlog #2 - This time wasn’t about adding new features. Instead, I spent the time refining Ellery from the ground up. I removed over 600 lines of UI code, simplified the interface, rewrote much of the copy, and cut away anything that distracted from the actual purpose of the product. The biggest lesson I’ve learned so far is that good software isn’t just about what you build, but it’s also about what you’re willing to remove. Every animation, button, label, and panel has to earn its place. Ellery feels much calmer now. The interface gets out of the way, and the focus stays where it should: understanding your data. Next up is a new demo video, and after that I’ll be taking on the first Stardance software challenge by building my own web operating system."}, {"post_id": 16019, "ts": "2026-06-26T00:27:08Z", "hours": 8.2911, "text": "Ellery AI - Devlog #1 I kept watching people open a spreadsheet, stare at it, and just… give up. The story was in there. They just couldn’t see it. So I started building Ellery to fix that. Honestly, I started where everyone starts: AI that summarizes your data. But I never trusted it. The summary sounded confident, changed every time I asked, and I could never tell if it was actually true. That’s useless if you’re about to put it in front of your boss.So I went visual instead - timelines, rank boards, an insight map. They looked great. But a pretty chart still makes you do the thinking. I’d basically built a nicer haystack.The thing that actually clicked was the Discovery Engine. Before anything gets drawn, Ellery reads your data and pulls out what matters - top items, outliers, what’s out of stock - as plain findings, each one traceable back to the exact rows it came from. No model, no guessing. Same data, same answers, every time.That changed everything downstream. Now the visualizations explain themselves, and you can export the whole thing to a slide in one click.Next up: turning those findings into recommendations, then a real narrative - and pointing it at NASA telemetry to see if it holds up beyond retail.It’s early, and I’m building it in the open. Follow along if that sounds like your kind of thing."}]...
|
Title: Ellery AI by @Ishaan_Jha | Stardance
Devlo Title: Ellery AI by @Ishaan_Jha | Stardance
Devlogs:
Ellery AI - Devlog #1 I kept watching people open a spreadsheet, stare at it, and just… give up. The story was in there. They just couldn’t see it. So I started building Ellery to fix that. Honestly, I started where everyone starts: AI that summarizes your data. But I never trusted it. The summary sounded confident, changed every time I asked, and I could never tell if it was actually true. That’s useless if you’re about to put it in front of your boss.So I went visual instead - timelines, rank boards, an insight map. They looked great. But a pretty chart still makes you do the thinking. I’d basically built a nicer haystack.The thing that actually clicked was the Discovery Engine. Before anything gets drawn, Ellery reads your data and pulls out what matters - top items, outliers, what’s out of stock - as plain findings, each one traceable back to the exact rows it came from. No model, no guessing. Same data, same answers, every time.That changed everything downstream. Now the visualizations explain themselves, and you can export the whole thing to a slide in one click.Next up: turning those findings into recommendations, then a real narrative - and pointing it at NASA telemetry to see if it holds up beyond retail.It’s early, and I’m building it in the open. Follow along if that sounds like your kind of thing.
Ellery Devlog #2 - This time wasn’t about adding new features. Instead, I spent the time refining Ellery from the ground up. I removed over 600 lines of UI code, simplified the interface, rewrote much of the copy, and cut away anything that distracted from the actual purpose of the product. The biggest lesson I’ve learned so far is that good software isn’t just about what you build, but it’s also about what you’re willing to remove. Every animation, button, label, and panel has to earn its place. Ellery feels much calmer now. The interface gets out of the way, and the focus stays where it should: understanding your data. Next up is a new demo video, and after that I’ll be taking on the first Stardance software challenge by building my own web operating system.
Devlog #3 - Making the app more open and dynamic: I am working on making the app feel less claustrophobic, adding/updating engines like the research engine, and making the UI more professional and multipage. Not commited and running yet, but almost there.
Devlog - how I accidentally almost shipped a lie detector that couldn’t detect lies: So Ellery already told you what was true about your data. Findings, plain English, click one and it peels open down to the exact rows. Nice. The problem was how it did that.Every finding carried a loose bag of numbers called evidence. And then, three separate times, a file called pull.js squinted at that bag and tried to reverse-engineer what the detector had been thinking. Three parallel switch (detector) statements. One to figure out which rows mattered, one to write the explanation sentence, one to write the derivation. Add a detector, edit four files, pray. Worst part: to figure out which rows a finding covered, pull.js re-ran the detector’s filter from scratch. Two copies of the same logic, living in different files, free to disagree. The finding says “3 records are low on stock,” the highlight lights up 4, and nobody notices for six months.The fix, and the part where I was wrongReplace the bag of numbers with an actual graph. Each finding now carries the computation that made it - max over a column, count over classified statuses - as nodes that hash to their own content, bottoming out at fingerprinted cells.I’d designed the graph nodes to include their computed value in their identity. Claude pushed back: separate identity from evaluation. The node names the computation; the value is what you get when you run it against data. Fine, sure, whatever - except it turns out that’s the entire ballgame, because now you get two fingerprints. One for the reasoning, one for the reasoning-applied-to-this-data. Which means the app can now tell you “your numbers changed but the logic didn’t” versus “the logic itself moved.” That’s a genuinely different product capability and it fell out of a definition change.Second thing I got wrong: I’d let the graph carry rowIndices. Row indices! In the evidence layer! That’s render state wearing a trenchcoat. Now it carries a witness - records addressed by content fingerprint - and the renderer figures out where they currently sit. Also, a haunting: Spent a solid while convinced the trace had 1,200px of unreachable content. Built a control experiment. Scrolling was fine. The real culprit was scroll-behavior: smooth - I was setting the scroll position and reading it back mid-animation, watching it clamp at 61.5px, and concluding the layout was broken. There was no bug. I nearly “fixed” a phantom. Small indignity: While all this was happening we discovered npm run lint was pointed at public/js, a directory that hasn’t existed since the frontend moved to the repo root. It had been linting nothing. For a while. Repointed it, and it immediately snitched on a pile of dead imports. Shipped: the derivation graph, two-fingerprint identity, a verify button that can actually say no, golden tests over the whole truth path, and a linter that lints. Deleted: more than I added, where it counted.
Cleaned up the site, fixed some very minor bugs, but the core of the site is set in stone. As stardance wraps up I want to make final minor tweaks, let claude scan through to find any bugs (dw i am under 30 percent ai, i just spent more than 30 percent of time on it with ai, but the code itself is def written more by me.) ready to ship soon –– also kept a changelog, so it has its own mini devlog list within. btw it will prob be in early access when shipped because i dont think it is at the level where it is worthy of a cost/payment, not even close, but it isn’t a bad app itself… i hope :)
Ships:
Ellery is being shipped. I spent the last stretch cleaning up the codebase, removing unused features, tightening the documentation, and making the reasoning behind each finding easier to verify. The goal was never just to make charts. It’s to help people understand what their data actually says, and trace every conclusion back to its evidence. The goal is to simplify the messy data....
|
1793724685.2566886
|
1793811085.2566886
|
|
16769
|
My first slack bot! by @harigo | Stardance
|
harigo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @harigo | Stardance
|
1793303446.1549804
|
1793908246.1549804
|
|
16770
|
Frictionless by @iiqw | Stardance
|
iiqw
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @iiqw | Stardance
|
1793289402.860052
|
1793894202.860052
|
|
16771
|
SpaceStationOS by @SpaceEvee | Stardance
|
SpaceEvee
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: SpaceStationOS by @SpaceEvee | Stardance
|
1793217313.210151
|
1793822113.210151
|
|
16772
|
Biosphere by @SDJasper | Stardance
|
SDJasper
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Biosphere by @SDJasper | Stardance
|
1793368472.2707682
|
1793973272.2707682
|
|
16773
|
OpenBoard by @Admanyx | Stardance
|
Admanyx
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: OpenBoard by @Admanyx | Stardance
|
1793483531.3665502
|
1794088331.3665502
|
|
16774
|
flight_pad by @samraat-756 | Stardance
|
samraat-756
|
1
|
3.0
|
15
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-16T05:51:29Z", "hours": 3.0, "multiplier": 5.0, "payout": 15, "blessing": "neutral", "text": "I made a 3x3 macro-pad with 2 rotary encoders, and is used to control common cockpit camera views for Microsoft flight simulator 2020 and 2024. The most challenging part of this project was first, wiring up the PCB, when laying out the tracks in the PCB editor, and then having to spend hours debugging custom firmware developed using QMK MSYS, and VS.Code, due to incorrect referencing, and setting up the compile process correctly to ensure a flawless compile via MSYS. To test my project, people need to make sure that even though they flash the firmware onto the board, they should also make sure to assign key binds in the simulator itself. I left that part out of the project, as everyone assigns key binds differently to their liking (in-game).", "repo": "https://github.com/samraatpchauhan-eng/flight_pad", "demo": ""}]...
|
[{"post_id": 9077, "ts": "2026 [{"post_id": 9077, "ts": "2026-06-15T05:02:20Z", "hours": 1.5831, "text": "Finally finished compiling the firmware for the flight_pad, after long hours of troubleshooting! I have effectively completed the project, but still need to make some tweaks to the case. After that, I plan to submit it!"}, {"post_id": 8874, "ts": "2026-06-14T19:33:55Z", "hours": 0.3169, "text": "Finished Designing the case for the FlightPad. It follows a simple, minimalist design asthetic, with a “FLIGHTPAD” engraving on top. This follows the sandwich style key mount."}, {"post_id": 8848, "ts": "2026-06-14T18:33:46Z", "hours": 0.7314, "text": "Finished designing the PCB via KiCad, which utlizes both sides of the board, and a 3x3 matrix system. However, only one of the two rotary encoders’ buttons will be utilized due to a lack of pins"}, {"post_id": 7918, "ts": "2026-06-13T06:16:53Z", "hours": 0.4411, "text": "Finished designing the schematics of the FlightSim_Pad, including 9 switches and 2 rotary encoders"}]...
|
Title: flight_pad by @samraat-756 | Stardance
Dev Title: flight_pad by @samraat-756 | Stardance
Devlogs:
Finished designing the schematics of the FlightSim_Pad, including 9 switches and 2 rotary encoders
Finished designing the PCB via KiCad, which utlizes both sides of the board, and a 3x3 matrix system. However, only one of the two rotary encoders’ buttons will be utilized due to a lack of pins
Finished Designing the case for the FlightPad. It follows a simple, minimalist design asthetic, with a “FLIGHTPAD” engraving on top. This follows the sandwich style key mount.
Finally finished compiling the firmware for the flight_pad, after long hours of troubleshooting! I have effectively completed the project, but still need to make some tweaks to the case. After that, I plan to submit it!
Ships:
I made a 3x3 macro-pad with 2 rotary encoders, and is used to control common cockpit camera views for Microsoft flight simulator 2020 and 2024. The most challenging part of this project was first, wiring up the PCB, when laying out the tracks in the PCB editor, and then having to spend hours debugging custom firmware developed using QMK MSYS, and VS.Code, due to incorrect referencing, and setting up the compile process correctly to ensure a flawless compile via MSYS. To test my project, people need to make sure that even though they flash the firmware onto the board, they should also make sure to assign key binds in the simulator itself. I left that part out of the project, as everyone assigns key binds differently to their liking (in-game)....
|
1793760694.0238483
|
1793847094.0238483
|
|
16775
|
KKKK by @hoshi | Stardance
|
hoshi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: KKKK by @hoshi | Stardance
|
1793778721.7367015
|
1794642721.7367015
|
|
16776
|
The Twistpad by @Cloud4D | Stardance
|
Cloud4D
|
1
|
16.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-09-08T02:19:35Z", "hours": 16.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a hackpad! I have decided to call my hackpad a Twistpad, since it has two rotary encoders. The Twistpad features a 3x3 grid of 9 keys, and two dials which are coded for volume and video playback. The 9 keys are mapped to F13-F21, meaning you can map it to anything you desire yourself quickly with no hassle. The case features a nice conical USB cutout to help guide the cable in, and there’s a wonderful little window in the top to peer inside at the brain of the device, the seeeduino!", "repo": "https://github.com/Cloud4D/Twistpad/blob/main/README.md", "demo": ""}]...
|
[{"post_id": 25618, "ts": "202 [{"post_id": 25618, "ts": "2026-07-10T00:28:26Z", "hours": 0.7325, "text": "Shipping time! Yeah, it’s time to finally ship my project, after waiting for the form to be fixed, and learning that I actually need to post more devlogs in order to actually count my hours, I’m about to fill out the submission form and ship my project :). Its been quite a ride."}, {"post_id": 13882, "ts": "2026-06-22T19:07:55Z", "hours": 1.1472, "text": "I found a problem, and fixed the problem. When coding, I noticed that I had messed up my matrix, so I went back to my schematic, fixed the schematic, fixed the PCB (thankfully it was easy), and then put the new PCB into the CAD model. Later, I plan on fixing my files and then finishing up the code, and then I should be done! I’ve attached a picture of the fixed schematic to this devlog."}, {"post_id": 12885, "ts": "2026-06-21T03:22:25Z", "hours": 7.2889, "text": "Time for my third devlog. I suppose I should be posting more, but the time tracker keeps bugging and I can’t write after finishing a amount of time. Between now and 4 days ago, I managed to finish up the case, I tackled multiple problems, such as figuring out holes and dimensions for the USB cutout and the rotary encoders and all that. I also made it all white so thats nice, better than that gray. I filleted the corners (I used that a bunch in the past few days), messed with geometry to make my cool little window to view into the Seeeduino module, realized that the window interfered with the keycaps, had to delete the window and make a new one, all fun stuff. The USB cutout was fun to make as a sketch, since I got to mess around with lines and rectangles to fillet the corners to make a rectangle with rounded corners and then realizing I could’ve just made a rectangle and filleted that, but oh well, it’s the joy of learning. I then formatted my files to get them ready for submission, and now I tackle the firmware. Wish me luck. Also Lapse still refuses to connect to Hackatime, I have 16 hours and 11 minutes on Lapse but only 5 hours and 25 minutes on Hackatime?? I hope it fixes itself soon."}, {"post_id": 10151, "ts": "2026-06-16T19:25:11Z", "hours": 5.3075, "text": "It’s been a while since I posted a devlog. I just got a bit busy but I guess it is time to sum up everything in I have done in the past few days! After finishing the guide hackpad, I took it upon myself to build my own custom hackpad (name pending). To begin, I went into Kicad’s schematics editor and created a schematic, using a matrix (thank you Gemini for teaching me what it is). I settled on a 3x3 keyboard with two dials, and after fiddling around with the layout and wiring and footprints and all that fun stuff, I was able to go to the PCB editor. This is where I spent the most amount of time. I spent about a day working through layouts of the LEDs, diodes, switches, and the Seeeduino. After that day, I tackled wiring everything up, and learned about vias. I don’t know what we’d do without them… they’re so helpful. I thought I was all good once I finished wiring things up… until I opened the DRC and ran it to find 500 errors. After changing some of the constraints, and realizing that I should make my 5V wire a bit wider, I managed to get the DRC down to around 100 errors, most of them being clearance errors. I spent a third day just fixing those and getting it down to 9 errors, all of which being simple silkscreen warnings. I also realized that my LEDs were existing in the same place as my switches, so I had to go back and redo ALL of the wiring for those, and then realized I was using the wrong footprint, and then I once more had to go back and redo all the wiring (lots of fun), but once I did that and fixed some issues with Edge.cuts, my PCB was all good to go! Finally we get to today, where I exported my PCB and put it into Fusion360, and drew and extruded the base and walls of the case (standoffs tomorrow). Also I don’t know why it only says I logged 3 hours, I’ve logged around 8 since my last post…"}, {"post_id": 7829, "ts": "2026-06-13T02:06:43Z", "hours": 1.5553, "text": "Fusion360 is very confusing… I did quite a bit of work today! I started by finishing up my PCB design on Kicad, which was quite fun. I’m looking forward to designing my own PCB. Designing the case on Fusion360 was a bit frustrating, since my only 3D modeling experience was with tinkercad a few years ago. ChatGPT was a big help in helping me understand the softwares. Using what I’ve learned here with the guide and whatnot, I’m excited to build my own custom macropad (maybe with a few dials to spice things up)"}]...
|
Title: The Twistpad by @Cloud4D | Stardance
Devlo Title: The Twistpad by @Cloud4D | Stardance
Devlogs:
Fusion360 is very confusing… I did quite a bit of work today! I started by finishing up my PCB design on Kicad, which was quite fun. I’m looking forward to designing my own PCB. Designing the case on Fusion360 was a bit frustrating, since my only 3D modeling experience was with tinkercad a few years ago. ChatGPT was a big help in helping me understand the softwares. Using what I’ve learned here with the guide and whatnot, I’m excited to build my own custom macropad (maybe with a few dials to spice things up)
It’s been a while since I posted a devlog. I just got a bit busy but I guess it is time to sum up everything in I have done in the past few days! After finishing the guide hackpad, I took it upon myself to build my own custom hackpad (name pending). To begin, I went into Kicad’s schematics editor and created a schematic, using a matrix (thank you Gemini for teaching me what it is). I settled on a 3x3 keyboard with two dials, and after fiddling around with the layout and wiring and footprints and all that fun stuff, I was able to go to the PCB editor. This is where I spent the most amount of time. I spent about a day working through layouts of the LEDs, diodes, switches, and the Seeeduino. After that day, I tackled wiring everything up, and learned about vias. I don’t know what we’d do without them… they’re so helpful. I thought I was all good once I finished wiring things up… until I opened the DRC and ran it to find 500 errors. After changing some of the constraints, and realizing that I should make my 5V wire a bit wider, I managed to get the DRC down to around 100 errors, most of them being clearance errors. I spent a third day just fixing those and getting it down to 9 errors, all of which being simple silkscreen warnings. I also realized that my LEDs were existing in the same place as my switches, so I had to go back and redo ALL of the wiring for those, and then realized I was using the wrong footprint, and then I once more had to go back and redo all the wiring (lots of fun), but once I did that and fixed some issues with Edge.cuts, my PCB was all good to go! Finally we get to today, where I exported my PCB and put it into Fusion360, and drew and extruded the base and walls of the case (standoffs tomorrow). Also I don’t know why it only says I logged 3 hours, I’ve logged around 8 since my last post…
Time for my third devlog. I suppose I should be posting more, but the time tracker keeps bugging and I can’t write after finishing a amount of time. Between now and 4 days ago, I managed to finish up the case, I tackled multiple problems, such as figuring out holes and dimensions for the USB cutout and the rotary encoders and all that. I also made it all white so thats nice, better than that gray. I filleted the corners (I used that a bunch in the past few days), messed with geometry to make my cool little window to view into the Seeeduino module, realized that the window interfered with the keycaps, had to delete the window and make a new one, all fun stuff. The USB cutout was fun to make as a sketch, since I got to mess around with lines and rectangles to fillet the corners to make a rectangle with rounded corners and then realizing I could’ve just made a rectangle and filleted that, but oh well, it’s the joy of learning. I then formatted my files to get them ready for submission, and now I tackle the firmware. Wish me luck. Also Lapse still refuses to connect to Hackatime, I have 16 hours and 11 minutes on Lapse but only 5 hours and 25 minutes on Hackatime?? I hope it fixes itself soon.
I found a problem, and fixed the problem. When coding, I noticed that I had messed up my matrix, so I went back to my schematic, fixed the schematic, fixed the PCB (thankfully it was easy), and then put the new PCB into the CAD model. Later, I plan on fixing my files and then finishing up the code, and then I should be done! I’ve attached a picture of the fixed schematic to this devlog.
Shipping time! Yeah, it’s time to finally ship my project, after waiting for the form to be fixed, and learning that I actually need to post more devlogs in order to actually count my hours, I’m about to fill out the submission form and ship my project :). Its been quite a ride.
Ships:
I made a hackpad! I have decided to call my hackpad a Twistpad, since it has two rotary encoders. The Twistpad features a 3x3 grid of 9 keys, and two dials which are coded for volume and video playback. The 9 keys are mapped to F13-F21, meaning you can map it to anything you desire yourself quickly with no hassle. The case features a nice conical USB cutout to help guide the cable in, and there’s a wonderful little window in the top to peer inside at the brain of the device, the seeeduino!...
|
1793764092.197007
|
1793850492.197007
|
|
16777
|
Retro snake game by @bluestacku116 | Stardance
|
bluestacku116
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Retro snake game by @bluestacku116 | Starda Title: Retro snake game by @bluestacku116 | Stardance...
|
1793177444.3745363
|
1793782244.3745363
|
|
16778
|
My very own WebOS by @hlaselim2012 | Stardance
|
hlaselim2012
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @hlaselim2012 | Starda Title: My very own WebOS by @hlaselim2012 | Stardance...
|
1793386177.7096806
|
1793990977.7096806
|
|
16779
|
Frictionless by @sushxnth | Stardance
|
sushxnth
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Frictionless by @sushxnth | Stardance
|
1793210037.4412115
|
1793814837.4412115
|
|
16780
|
My very own WebOS by @vihaanadarsha018 | Stardance
|
vihaanadarsha018
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @vihaanadarsha018 | St Title: My very own WebOS by @vihaanadarsha018 | Stardance...
|
1793462226.8469234
|
1794067026.8469234
|
|
16781
|
FRC Shop Assistant by @ibosigma | Stardance
|
ibosigma
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: FRC Shop Assistant by @ibosigma | Stardance
|
1793213492.0761979
|
1793818292.0761979
|
|
16782
|
My first slack bot! by @Rocket | Stardance
|
Rocket
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Rocket | Stardance
|
1793191763.1291275
|
1793796563.1291275
|
|
16783
|
My awesome macropad! by @VoidChris | Stardance
|
VoidChris
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @VoidChris | Starda Title: My awesome macropad! by @VoidChris | Stardance...
|
1792929159.0472748
|
1793793159.0472748
|
|
16784
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1792932819.0889246
|
1793796819.0889246
|
|
16785
|
My very own WebOS by @SpacerCoder | Stardance
|
SpacerCoder
|
1
|
2.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-05T11:06:04Z", "hours": 2.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a almost ‘real’ OS, and the coolest part in my opinion is that you can customize it how you like. There’s different apps and other cool bits that really bring it together. The challenging part in my opinion was creating the different apps within the bottom dock area. Another cool feature is the ‘loading’ screen where when you first open the website ‘os’ theres a terminal loading screen type of interface, which I am really happy with. To use, simply click on ‘try project’ wait for the interface to load, and you can then try the notes app, and other apps in the dock area. Have fun!", "repo": "https://github.com/SwiftProGrammer178611/StarDanceWebOS", "demo": "https://star-dance-web-os.vercel.app/"}]...
|
[{"post_id": 22580, "ts": "202 [{"post_id": 22580, "ts": "2026-07-05T03:23:01Z", "hours": 0.2594, "text": "added some more apps, like terminal and notes"}, {"post_id": 22486, "ts": "2026-07-04T23:36:37Z", "hours": 0.9117, "text": "trying to add a bottom navigation system!"}, {"post_id": 7375, "ts": "2026-06-12T09:31:41Z", "hours": 0.3564, "text": "Started working on the OS! Let’s see where this takes us"}]...
|
Title: My very own WebOS by @SpacerCoder | Stardan Title: My very own WebOS by @SpacerCoder | Stardance
Devlogs:
Started working on the OS! Let’s see where this takes us
trying to add a bottom navigation system!
added some more apps, like terminal and notes
Ships:
I made a almost ‘real’ OS, and the coolest part in my opinion is that you can customize it how you like. There’s different apps and other cool bits that really bring it together. The challenging part in my opinion was creating the different apps within the bottom dock area. Another cool feature is the ‘loading’ screen where when you first open the website ‘os’ theres a terminal loading screen type of interface, which I am really happy with. To use, simply click on ‘try project’ wait for the interface to load, and you can then try the notes app, and other apps in the dock area. Have fun!...
|
1793692579.3857877
|
1793778979.3857877
|
|
16786
|
My very own WebOS by @Katraca51 | Stardance
|
Katraca51
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Katraca51 | Stardance
|
1793368406.3054264
|
1793973206.3054264
|
|
16787
|
My very own WebOS by @Abhisumat | Stardance
|
Abhisumat
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Abhisumat | Stardance
|
1793368295.988334
|
1793973095.988334
|
|
16788
|
My awesome macropad! by @Miron | Stardance
|
Miron
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Miron | Stardance
|
1793490636.7096512
|
1794095436.7096512
|
|
16789
|
My very own WebOS by @Silver | Stardance
|
Silver
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @Silver | Stardance
|
1793199267.4936604
|
1793804067.4936604
|
|
16790
|
Hohmann Transfer Orbit Visualization by @trumanhea Hohmann Transfer Orbit Visualization by @trumanheaston | Stardance...
|
trumanheaston
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Hohmann Transfer Orbit Visualization by @tr Title: Hohmann Transfer Orbit Visualization by @trumanheaston | Stardance...
|
1793534119.0018435
|
1794138919.0018435
|
|
16791
|
My awesome macropad! by @jaiset | Stardance
|
jaiset
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @jaiset | Stardance
|
1793526730.5914004
|
1794131530.5914004
|
|
16792
|
My very own WebOS by @AbhiCheb | Stardance
|
AbhiCheb
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @AbhiCheb | Stardance
|
1793332068.4371147
|
1793936868.4371147
|
|
16793
|
Stream Deck by @Moslo | Stardance
|
Moslo
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Stream Deck by @Moslo | Stardance
|
1793242458.0047548
|
1793847258.0047548
|
|
16794
|
My awesome macropad! by @Heisemberg | Stardance
|
Heisemberg
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Heisemberg | Stard Title: My awesome macropad! by @Heisemberg | Stardance...
|
1793450959.8411224
|
1794055759.8411224
|
|
16795
|
MAGNUS: DIY chess playing robot by @Leo_Zannoni | MAGNUS: DIY chess playing robot by @Leo_Zannoni | Stardance...
|
Leo_Zannoni
|
1
|
8.0
|
0
|
[{"ship_num": 1, "ts": "2026-1 [{"ship_num": 1, "ts": "2026-10-26T04:59:59Z", "hours": 8.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "What I made MAGNUS is a robot that plays chess against you on a real wooden board that was recycled like most of the parts of the project and says every move out loud in Spanish. You play your move by hand. A phone camera above the board (through Iriun) reads the ArUco marker on top of each piece and works out what you played. Stockfish picks the reply, and a 2-joint arm picks up the piece with a magnet and puts it on its new square. It handles captures, castling, en passant and promotion, and when it finishes it moves out of the way so it doesn’t block your view or the camera’s. The problem it solves Playing chess on a real board usually means you need another person sitting in front of you. Chess apps solve that, but then you’re staring at a screen, which is hard for people with low vision, older players who don’t get along with phones, and anyone who just learns better with real pieces in their hands. I wanted something in between: a physical opponent that’s always available and doesn’t make you look at a screen. The QoL improvements You can play a real-board game alone. The robot moves its own pieces, so you never have to make its moves for it or check a screen to see what it played. It talks. Every robot move is spoken in Spanish, so you can follow the game by ear. It also warns you if you made an illegal move and reminds you when it’s your turn if you take too long. This is the main accessibility part: someone with low vision or someone who can’t read chess notation can still follow what’s happening. It adapts to you. There are 10 difficulty levels, from a beginner level that makes mistakes on purpose up to full Stockfish, and you can change them in the middle of a game from a simple web panel. It also comments on how good or bad a move was, so beginners get feedback while they play, kind of like a coach. What was challenging The arm, by far. The mBot2 encoder motors don’t remember where they are when they turn on, so the arm has to find its zero against physical stops every time it starts. I tried a 3:1 reduction on the shoulder, couldn’t get it to work, and ended up with direct drive. Instead of inverse kinematics I recorded the motor angles for all 64 squares with the motors powered, because the arm bends differently when you move it by hand. The gripper went through several versions until I added a lift step. Without it, the magnet dragged pieces across the board and knocked over the neighbors. Smaller things also cost me hours: magnet holes printed at exactly 10 mm were too tight, so I made them 10.1 to 10.2 mm. The CyberPi only sees 2.4 GHz WiFi and doesn’t report its IP, so my Mac runs a TCP server and the board connects to it. And mBlock’s mlink kept locking the serial port. What I’m proud of It plays full games by itself and narrates them. I’m also happy with the magnet system: a 12x3 mm N52 on the arm, two 10x2 mm magnets in each piece (one on top for the arm, one underneath for the board) and a 6x3 mm magnet under every square. The arm grabs one piece and the ones next to it stay where they are. Almost all of the physical parts I designed and printed myself on a Bambu Lab A1 mini.", "repo": "https://github.com/LeoZ24/MAGNUS_Chess_Robot/tree/master", "demo": ""}]...
|
[{"post_id": 81134, "ts": "202 [{"post_id": 81134, "ts": "2026-10-20T01:00:50Z", "hours": 8.3128, "text": "What MAGNUS is MAGNUS is a robot that plays chess on a real board against a person and says its moves out loud in Spanish. I’m building it for PRONAFECYT 2026, Costa Rica’s national science fair, and the voice is there for accessibility: you can follow the game without looking at a screen. I started on february with my first 3D models. Today it plays full games by itself and narrates them. About the hours Hackatime only logged about 8.5 h, because it only counts time in the code editor when i downloaded the app. Most of the work was CAD, printing, assembling and testing the arm. My log puts the real total at 350+ hours Vision Every piece is a 22.5 mm disc with an ArUco 4x4_50 marker and a white ring around it for contrast. The four board corners have their own markers, so the board is found from any camera angle. The camera is my phone through Iriun. A piece only counts after 5 detections in a row, and a GameTracker compares what the camera sees against every legal move to work out what the human played, including castling and en passant. Engine Stockfish runs through python-chess with 10 difficulty levels. Stockfish can’t play below about 1320 Elo, so the four easiest levels choose worse moves on purpose. Every move comes with metadata for captures, castling, en passant and promotion, so the arm never has to know any chess. The arm Shoulder and elbow use the encoder motors from the mBot2 kit on a CyberPi, with a LEGO Technic frame plus printed parts. I tried a 3:1 reduction on the shoulder, couldn’t make it work, and direct drive turned out to be enough. Instead of inverse kinematics I recorded the motor angles for all 64 squares once (teach and playback), with the motors powered, because the arm bends differently when you move it by hand. The encoders are incremental, so the arm homes against physical stops every time it starts. Magnets and the gripper The arm carries a 12x3 mm N52 magnet that grabs a piece from about 8 mm away. Each piece has two 10x2 mm magnets, one on top for the arm and one underneath for the board, and every square has a 6x3 mm magnet below it. Neighboring pieces 32 mm away don’t move. A servo lowers the magnet, lifts the piece and releases it. Without the lift step the arm dragged pieces and knocked over the neighbors. Problems I had to solve Magnet holes modeled at exactly 10 mm were too tight, so I made them 10.1 to 10.2 mm to allow for FDM tolerance. The CyberPi doesn’t report its IP, so my Mac runs a TCP server and the CyberPi connects to it as a client. The CyberPi only sees 2.4 GHz WiFi. mBlock’s mlink kept the serial port locked until I ran pkill -f mlink. How the software is organized There are three nodes (vision, engine and arm) that talk through typed messages, ROS2 style. Each hardware part has a fake backend, so the 482 tests run without the robot, and there’s a fully simulated pipeline for testing a whole game. What’s next Tuning arm precision: re-recording the squares where the magnet doesn’t land centered and testing the robot more with people with blind people. Also im working on a demo video with the robot working coming soon"}, {"post_id": 7867, "ts": "2026-06-13T03:49:51Z", "hours": 0.4319, "text": "Added the 3d chess models for the project"}]...
|
Title: MAGNUS: DIY chess playing robot by @Leo_Zan Title: MAGNUS: DIY chess playing robot by @Leo_Zannoni | Stardance
Devlogs:
Added the 3d chess models for the project
What MAGNUS is MAGNUS is a robot that plays chess on a real board against a person and says its moves out loud in Spanish. I’m building it for PRONAFECYT 2026, Costa Rica’s national science fair, and the voice is there for accessibility: you can follow the game without looking at a screen. I started on february with my first 3D models. Today it plays full games by itself and narrates them. About the hours Hackatime only logged about 8.5 h, because it only counts time in the code editor when i downloaded the app. Most of the work was CAD, printing, assembling and testing the arm. My log puts the real total at 350+ hours Vision Every piece is a 22.5 mm disc with an ArUco 4x4_50 marker and a white ring around it for contrast. The four board corners have their own markers, so the board is found from any camera angle. The camera is my phone through Iriun. A piece only counts after 5 detections in a row, and a GameTracker compares what the camera sees against every legal move to work out what the human played, including castling and en passant. Engine Stockfish runs through python-chess with 10 difficulty levels. Stockfish can’t play below about 1320 Elo, so the four easiest levels choose worse moves on purpose. Every move comes with metadata for captures, castling, en passant and promotion, so the arm never has to know any chess. The arm Shoulder and elbow use the encoder motors from the mBot2 kit on a CyberPi, with a LEGO Technic frame plus printed parts. I tried a 3:1 reduction on the shoulder, couldn’t make it work, and direct drive turned out to be enough. Instead of inverse kinematics I recorded the motor angles for all 64 squares once (teach and playback), with the motors powered, because the arm bends differently when you move it by hand. The encoders are incremental, so the arm homes against physical stops every time it starts. Magnets and the gripper The arm carries a 12x3 mm N52 magnet that grabs a piece from about 8 mm away. Each piece has two 10x2 mm magnets, one on top for the arm and one underneath for the board, and every square has a 6x3 mm magnet below it. Neighboring pieces 32 mm away don’t move. A servo lowers the magnet, lifts the piece and releases it. Without the lift step the arm dragged pieces and knocked over the neighbors. Problems I had to solve Magnet holes modeled at exactly 10 mm were too tight, so I made them 10.1 to 10.2 mm to allow for FDM tolerance. The CyberPi doesn’t report its IP, so my Mac runs a TCP server and the CyberPi connects to it as a client. The CyberPi only sees 2.4 GHz WiFi. mBlock’s mlink kept the serial port locked until I ran pkill -f mlink. How the software is organized There are three nodes (vision, engine and arm) that talk through typed messages, ROS2 style. Each hardware part has a fake backend, so the 482 tests run without the robot, and there’s a fully simulated pipeline for testing a whole game. What’s next Tuning arm precision: re-recording the squares where the magnet doesn’t land centered and testing the robot more with people with blind people. Also im working on a demo video with the robot working coming soon
Ships:
What I made MAGNUS is a robot that plays chess against you on a real wooden board that was recycled like most of the parts of the project and says every move out loud in Spanish. You play your move by hand. A phone camera above the board (through Iriun) reads the ArUco marker on top of each piece and works out what you played. Stockfish picks the reply, and a 2-joint arm picks up the piece with a magnet and puts it on its new square. It handles captures, castling, en passant and promotion, and when it finishes it moves out of the way so it doesn’t block your view or the camera’s. The problem it solves Playing chess on a real board usually means you need another person sitting in front of you. Chess apps solve that, but then you’re staring at a screen, which is hard for people with low vision, older players who don’t get along with phones, and anyone who just learns better with real pieces in their hands. I wanted something in between: a physical opponent that’s always available and doesn’t make you look at a screen. The QoL improvements You can play a real-board game alone. The robot moves its own pieces, so you never have to make its moves for it or check a screen to see what it played. It talks. Every robot move is spoken in Spanish, so you can follow the game by ear. It also warns you if you made an illegal move and reminds you when it’s your turn if you take too long. This is the main accessibility part: someone with low vision or someone who can’t read chess notation can still follow what’s happening. It adapts to you. There are 10 difficulty levels, from a beginner level that makes mistakes on purpose up to full Stockfish, and you can change them in the middle of a game from a simple web panel. It also comments on how good or bad a move was, so beginners get feedback while they play, kind of like a coach. What was challenging The arm, by far. The mBot2 encoder motors don’t remember where they are when they turn on, so the arm has to find its zero against physical stops every time it starts. I tried a 3:1 reduction on the shoulder, couldn’t get it to work, and ended up with direct drive. Instead of inverse kinematics I recorded the motor angles for all 64 squares with the motors powered, because the arm bends differently when you move it by hand. The gripper went through several versions until I added a lift step. Without it, the magnet dragged pieces across the board and knocked over the neighbors. Smaller things also cost me hours: magnet holes printed at exactly 10 mm were too tight, so I made them 10.1 to 10.2 mm. The CyberPi only sees 2.4 GHz WiFi and doesn’t report its IP, so my Mac runs a TCP server and the board connects to it. And mBlock’s mlink kept locking the serial port. What I’m proud of It plays full games by itself and narrates them. I’m also happy with the magnet system: a 12x3 mm N52 on the arm, two 10x2 mm magnets in each piece (one on top for the arm, one underneath for the board) and a 6x3 mm magnet under every square. The arm grabs one piece and the ones next to it stay where they are. Almost all of the physical parts I designed and printed myself on a Bambu Lab A1 mini....
|
1793797015.5641189
|
1793883415.5641189
|
|
16796
|
FalAmrit by @Amika | Stardance
|
Amika
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: FalAmrit by @Amika | Stardance
|
1793181031.378977
|
1793785831.378977
|
|
16797
|
ROME OS by @mbghg | Stardance
|
mbghg
|
0
|
0.63
|
0
|
[]
|
[{"post_id": 6999, "ts": "2026 [{"post_id": 6999, "ts": "2026-06-11T19:06:29Z", "hours": 0.6297, "text": "I made the login screen of the OS. added taskbar: -top: - version - SPQR - clock -bottom: - Placeholder for apllications register user and login with password remembers user after closing and opening"}]...
|
Title: ROME OS by @mbghg | Stardance
Devlogs:
I m Title: ROME OS by @mbghg | Stardance
Devlogs:
I made the login screen of the OS. added taskbar: -top: - version - SPQR - clock -bottom: - Placeholder for apllications register user and login with password remembers user after closing and opening...
|
1793490547.4940066
|
1794095347.4940066
|
|
16798
|
My awesome macropad! by @vihaanadarsha018 | Starda My awesome macropad! by @vihaanadarsha018 | Stardance...
|
vihaanadarsha018
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @vihaanadarsha018 | Title: My awesome macropad! by @vihaanadarsha018 | Stardance...
|
1793490992.3992727
|
1794095792.3992727
|
|
16799
|
3D engine in terminal by @Sudsy | Stardance
|
Sudsy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: 3D engine in terminal by @Sudsy | Stardance
|
1793552162.0579023
|
1794156962.0579023
|
|
16800
|
My awesome macropad! by @s_amia_dilauro | Stardanc My awesome macropad! by @s_amia_dilauro | Stardance...
|
s_amia_dilauro
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @s_amia_dilauro | S Title: My awesome macropad! by @s_amia_dilauro | Stardance...
|
1793332089.1674216
|
1793936889.1674216
|