|
3381
|
WonderWild by @fernandazam319 | Stardance
|
fernandazam319
|
0
|
0.8
|
0
|
[]
|
[{"post_id": 24263, "ts": "202 [{"post_id": 24263, "ts": "2026-07-07T18:30:34Z", "hours": 0.7981, "text": "i made the simple mechanics for my game and created the sprites. next step: add images to make it less plain"}]...
|
Title: WonderWild by @fernandazam319 | Stardance
Title: WonderWild by @fernandazam319 | Stardance
Devlogs:
i made the simple mechanics for my game and created the sprites. next step: add images to make it less plain...
|
1792774525.3603978
|
1793379325.3603978
|
|
3382
|
Advanced Weather Station by @CircuitCyborg | Stard Advanced Weather Station by @CircuitCyborg | Stardance...
|
CircuitCyborg
|
0
|
15.05
|
0
|
[]
|
[{"post_id": 68863, "ts": "202 [{"post_id": 68863, "ts": "2026-09-15T22:07:30Z", "hours": 9.1072, "text": "Well Well Well Seems a few months have passed since my last devlog. I guess it’s time to update the two people watching (HI). In the last few months I have completed it seems about 9 hours of tracked time. In this time I have: Reworked how the base station PCB is designed for better ergonomics, created V1 of the Base station case, the Power injector case V1, Wind Direction module V1, the outdoor temp and humidity sensor module V1. I also began working on attaching the sensor modules to the sensor tree. Up next create a base code to make this function, and redesign the base station case for the new form of the base station PCB. I will also begin to set up the shipping Repository for the project. Now that I’ve shown that I’m still alive, signing out for the next few days since the virtual event is almost over."}, {"post_id": 5171, "ts": "2026-06-08T21:05:11Z", "hours": 5.9472, "text": "PCB Design. Over the last week, I have created the schematic and footprint for the Base station, and the POE Injector. I then created a few different versions throughout the week for the sensor module. One version had the compute module separate from the sensors to be able to place the Pico for computation indoors, then just have an RJ45 cable between that and the sensors. The next version attached almost all sensors to the compute module to simplify, and used potentiometers for the wind speed and direction. The current version uses hall effect sensors for a rain gauge, wind speed, and wind direction. More updates soon."}]...
|
Title: Advanced Weather Station by @CircuitCyborg Title: Advanced Weather Station by @CircuitCyborg | Stardance
Devlogs:
PCB Design. Over the last week, I have created the schematic and footprint for the Base station, and the POE Injector. I then created a few different versions throughout the week for the sensor module. One version had the compute module separate from the sensors to be able to place the Pico for computation indoors, then just have an RJ45 cable between that and the sensors. The next version attached almost all sensors to the compute module to simplify, and used potentiometers for the wind speed and direction. The current version uses hall effect sensors for a rain gauge, wind speed, and wind direction. More updates soon.
Well Well Well Seems a few months have passed since my last devlog. I guess it’s time to update the two people watching (HI). In the last few months I have completed it seems about 9 hours of tracked time. In this time I have: Reworked how the base station PCB is designed for better ergonomics, created V1 of the Base station case, the Power injector case V1, Wind Direction module V1, the outdoor temp and humidity sensor module V1. I also began working on attaching the sensor modules to the sensor tree. Up next create a base code to make this function, and redesign the base station case for the new form of the base station PCB. I will also begin to set up the shipping Repository for the project. Now that I’ve shown that I’m still alive, signing out for the next few days since the virtual event is almost over....
|
1793224087.2525046
|
1793828887.2525046
|
|
3383
|
My awesome macropad! by @Sharad | Stardance
|
Sharad
|
0
|
0.9
|
0
|
[]
|
[{"post_id": 10458, "ts": "202 [{"post_id": 10458, "ts": "2026-06-17T05:57:41Z", "hours": 0.8992, "text": "I am working on my macropad. Still getting used to VS Code as it is my first time, so it is a bit of a learning curve!"}]...
|
Title: My awesome macropad! by @Sharad | Stardance Title: My awesome macropad! by @Sharad | Stardance
Devlogs:
I am working on my macropad. Still getting used to VS Code as it is my first time, so it is a bit of a learning curve!...
|
1793166885.4413571
|
1793771685.4413571
|
|
3384
|
My awesome macropad! by @marzbanc26 | Stardance
|
marzbanc26
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @marzbanc26 | Stard Title: My awesome macropad! by @marzbanc26 | Stardance...
|
1793256609.6276355
|
1793861409.6276355
|
|
3385
|
My HACKPAD!!! by @Quickmando | Stardance
|
Quickmando
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My HACKPAD!!! by @Quickmando | Stardance
|
1793436695.0538278
|
1794041495.0538278
|
|
3386
|
My first slack bot! by @samda0824 | Stardance
|
samda0824
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @samda0824 | Stardan Title: My first slack bot! by @samda0824 | Stardance...
|
1793191947.8102384
|
1793796747.8102384
|
|
3387
|
My awesome macropad! by @wannabeoiiiiii | Stardanc My awesome macropad! by @wannabeoiiiiii | Stardance...
|
wannabeoiiiiii
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @wannabeoiiiiii | S Title: My awesome macropad! by @wannabeoiiiiii | Stardance...
|
1793432981.1179392
|
1794037781.1179392
|
|
3388
|
My awesome macropad! by @BugHunter | Stardance
|
BugHunter
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @BugHunter | Starda Title: My awesome macropad! by @BugHunter | Stardance...
|
1792795775.3377469
|
1793400575.3377469
|
|
3389
|
Untitled project by @aquoria | Stardance
|
aquoria
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @aquoria | Stardance
|
1793238581.067626
|
1793843381.067626
|
|
3390
|
Rat clone by @youngzheimer | Stardance
|
youngzheimer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Rat clone by @youngzheimer | Stardance
|
1793444034.363696
|
1794048834.363696
|
|
3391
|
Run 999 miles to beat the game! by @PhantomPorter Run 999 miles to beat the game! by @PhantomPorter | Stardance...
|
PhantomPorter
|
0
|
2.39
|
0
|
[]
|
[{"post_id": 6629, "ts": "2026 [{"post_id": 6629, "ts": "2026-06-11T03:36:33Z", "hours": 1.2428, "text": "Worked on a stage hazard that requires you to slide under. This came with changing how collisions work at all, which I couldn’t finish for right now."}, {"post_id": 3236, "ts": "2026-06-06T02:00:39Z", "hours": 1.1447, "text": "Added a parry action for the player, with sounds and all."}]...
|
Title: Run 999 miles to beat the game! by @Phantom Title: Run 999 miles to beat the game! by @PhantomPorter | Stardance
Devlogs:
Added a parry action for the player, with sounds and all.
Worked on a stage hazard that requires you to slide under. This came with changing how collisions work at all, which I couldn’t finish for right now....
|
1793148786.2241535
|
1793753586.2241535
|
|
3392
|
My awesome macropad! by @priyamk | Stardance
|
priyamk
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @priyamk | Stardanc Title: My awesome macropad! by @priyamk | Stardance...
|
1793159441.6701827
|
1793764241.6701827
|
|
3393
|
My awesome macropad! by @TCNCRTR | Stardance
|
TCNCRTR
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @TCNCRTR | Stardanc Title: My awesome macropad! by @TCNCRTR | Stardance...
|
1792932763.732745
|
1793796763.732745
|
|
3394
|
My awesome macropad! by @justjason | Stardance
|
justjason
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @justjason | Starda Title: My awesome macropad! by @justjason | Stardance...
|
1793447510.945147
|
1794052310.945147
|
|
3396
|
black hole by @siddharth_karuturi | Stardance
|
siddharth_karuturi
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: black hole by @siddharth_karuturi | Stardan Title: black hole by @siddharth_karuturi | Stardance...
|
1793346995.7683876
|
1793951795.7683876
|
|
3397
|
Moonshine by @kritik | Stardance
|
kritik
|
1
|
58.21
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-07-08T01:46:24Z", "hours": 47.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I made a materials science engine meant to try and come up with candidates for novel materials with a high likleyhood of stability and validity for more advanced algorithms. The challenging part was integrating all the different tools being used, as well as perfectly tuning all tools to create accurate structures in as little time as possible. I am proud of the beautiful structures created by this algorithm. What to know to test this project is that its very unlikely a new material will be found on the first few tries, this has to be run for a while so start at the beta processing layer and run what is in the Alpha Arrays file. There is also lots of inaccuracies in this pipeline due to using off the self locally hosted LLM’s so you might have to run each layer a few times and not all candidates will be made.", "repo": "https://github.com/K200811/Project-MoonshineV2-Live", "demo": "https://github.com/K200811/Project-MoonshineV2-Live/releases/tag/v1.0.0"}]...
|
[{"post_id": 28069, "ts": "202 [{"post_id": 28069, "ts": "2026-07-14T02:58:00Z", "hours": 6.2922, "text": "IMPORTANT NOTE MOONSHINE TAKES A FEW HOURS TO RUN FOR THE BETA AND GAMMA LAYERS, SO JUST CHECK THE TERMINAL THAT OPENS UP WITH THE UI TO MAKE SURE EVERYTHING IS WORKING AND JUST WAIT YOU CAN ALSO SEE IT WORKING THROUGH THAT TERMINAL OUTPUT JUST MAKE SURE TO DOWNLOAD OLLAMA AND THE TWO AI MODELES THAT GO WITH IT, GEMMA THREE AND DEEPSEAK R1 . . . . In this last devlog I am showing how I turned my python project into a file that anyone can download and use on there Mac device without fiddling with python files and github repos. And boy was that a adventure. Firstly I know quite a bit about building python projects and everthing to do with building projects inside VSCode. I know ABSOLUTLY NOTHING about turning that into something others can easily use. The battles I faught with learning about file paths and directories and temp folders and the whole bajazz was enough to make Roman warriors run. But nontheless with Claude as my sensie and enough caffine to send a todler to the moon I was able to figure it out and Im going to outline some of it now. Firstly this project is a multi script project where you run each stage (Alpha - Epsilon) and check the output for each and move onto the next stage and so on jsut becuase thats how I liked it best. Now to comuncate information through differtent scripts I used JSON’s. But when packaging a python project you must make it so that insted of just writting with open (, …) the filename cant just be a name, it has to be a whole path. Learning that fact and how to implement that was a strugle. Then came the strugle of makeing a master script. At the begining of my master script I was importing each python file for each stage. That mixed with not having a run function in each stage and using if “name” == “ main ” to run all the main code for each stage resulted in a kathuple amount of erros and problems such as scripts not running, multiple windows being created, and more. The last bug problem was how to package everything together. I tried command after command with nothing working, only to then learn of how I must move all my files into the Dict folder created when packaging in order to make suer everything works properly. Now I just have to put this in a github release and everyone can use the executable file I have made."}, {"post_id": 26802, "ts": "2026-07-11T20:06:17Z", "hours": 4.9181, "text": "Realizing the importance of A UI for this I had base 44 whip up a UI you can connect to the python backend once you download it so you can see the stats of the algorithm running"}, {"post_id": 24366, "ts": "2026-07-07T21:33:11Z", "hours": 30.3122, "text": "MOONSHINE PROJECT FULLY FINISHED. In this devlog I am going to share how I was able to finally complete the Moonshine algorithm into a system that can autonomously generate novel crystal structures. Firstly The Beta and Gamma processing layers were changed to use locally hosted ollama models for the AI reasoning capabilities. In the Gamma layer a few changes were made as well. After constant experimenting with different AI models and architectures for the pipeline this was the one that I landed on. In the Gamma layer Ollama uses Deepseek to generate parameters for PyXtal crystal structure generation. I learned through constant experimentation that the PyXtal library’s randomness for crystal structure generation is much worse than I thought initially. Initially I thought with 10-20 tries the right structure would be generated. But no. Now what happens is the pipeline takes the parameters generated by deepseek and creates 500 pyXtal crystal structures. This adds about 3 minutes to the compute time for each candidate coming in from the Beta Processing Layer, but increases total accuracy by about 40%. The reason this helps is because PyXtal doesn’t get the structure right the first time, so by creating 500 and then picking the lowest energy generation we get the best structure we can from PyXtal. The next change made was the CHGNet relaxation phase inside of the Gamma Processing Layer. Initially I was using a random combination of convergence values, and structure optimizers. I changed that so now there are two layers to the relaxation phase. The first phase is a rough, low level, coarse relaxation that creates a rough initial structure, this is done by keeping the convergence value at 0.01 and using the basic UnitCellFillter optimizer. In the more stricter final relaxation pass the convergence value is tightened to 0.001 and the more advanced FrechetCellFilter is used. This has two benefits. firstly after the first pass the structure can be checked for validity and discarded if it is invalid before moving onto more expensive relaxation, secondly the structure created by PyXtal is relaxed more gently, by first getting an initial form and then being tightened down to its final form instead of taking the initial broken PyXtal structure and immediately forcing it into a tight final structure. It’s kind of like working with clay when making pots. Next comes the new Delta Processing Layer. The delta processing layer tests the structures made by the Gamma Processing layer further by subjecting it to a suite of tests. Atomic overlap, composition, coordination number plusability, oxidation number plusability, and structure matching against the materials project is tested on the crystal. This is done five times per candidate in beta since gamma produces five structures per candidate. This effectively tests validity and novelty for each structure. Finally comes the new Epsilon Processing Layer. This layer analyzes the structures created to give a better understanding of what we created, along with creating slab structures for the unit cell structure. Slab structures are just unit cell structures repeated into 3d space. Unit cell analysis returns density, unit cell volume, lattice parameters, final space group symmetry, local atomic geometry, bond lengths, bond angles, and prototype classification. Then comes the slab analisis. First the slabs are created by pymatgen, the main library used in this entire project, and analyzed for the following: surface symmetry, polarity, surface normal vectors, scale factors, center of mass alignment, termination layer composition, candidate adsorption sites, and total surface area. Slabs are created along the three Miller indices; there are just numbers that tell how the crystal is sliced in 3d space in reference to the three axes, (1,0,0) (1,1,0) and (1,1,1). And that’s the algorithm I spent over a month on. Now I have to just leave it running for a while and see if it finds any new crystal materials."}, {"post_id": 10331, "ts": "2026-06-17T00:19:18Z", "hours": 8.4331, "text": "I finished the Gamma Processing layer. This is the part of the file that takes in the formulas we created and screened in the Beta Processing Layer and then creates there structures and run a few initial validity tests on them. . First we start off with importing all the infinity stones of materials science. Then we get into our functions . First comes the Initial Super Gamma function. Ooooo fancyyy. No just kidding, I named everything so that I could tell which step of the process it came in just by reading the name. Initial tells me its the first and the Keyword super tells me its one of if not the first function to be run. Since keeping the order of every function run is super important for this to be built well this helps a lot. In the Initial Super Gamma Function we have a LLM, whos job is to take a look at the formula we created in the Beta Processing Layer and figure out what are the correct inputs to put into PyXtal for that formula. I will get into PyXtal in a bit . Next comes the SubGammaFunction. This function is nothing more than a overglorified string parser. It takes the output from the LLM, finds the key information we want, Dim, Group, Species, NumIons, and extracts them into variables we can input into PyXtal. Now all that seams straight forward right? So you can imagine my surprise when I was getting error after error in parsing the LLM response. I was so confused for some reason it could not extract the species from the response???? Yeah no it turned out I spelled species wrong in the function call. :) I know I make complaint jokes but its bugs, erros, and moments like that , that really make coding such a laugh, even those moments I really so enjoy. . Now back to the project! After parsing out all the information we can finally get to the interesting part 😈. CREATING AWESOME CRYSTAL STRUCTURES!!!!! PyXtal is a python tool that lets us randomly generate structures that don’t disobey fundamental laws of chemistry, such as Wyckoff positioning. The main challenge I had to overcome here was maintaining the structural group I had assigned to this crystal. PyXtal would be actively trying to create the best structure it thought was best but I wanted to preserve certain geometries to test since that is the most important thing in crystal creation . ANOTHER HUGE PROBLEM, I KEPT RUNNING OUT OF FREE CREDITS TO USE THE HUGGINGFACE AI MODELS. In the middle I tried to switch to Ollama locally hosted models I have before, but the remembered why I left them, THEY TAKE FOREVER. . After we create the PyXtal structures we run them through CHGNet to relax the structures, PyXtal SUCKS at creating low energy, high stability structures, its good at creating structures that don’t break certain rules such as Wyckoff positioning. After CHGNet relaxes the structure. It gives up the Stress values on the structure and the forces acting on the lattice of the crystal. We run 2 small loops to check each value and make sure its under 0.1 which is the value that is considered unstable for both metrics. If it passes the tests then its structure file is stored."}, {"post_id": 5973, "ts": "2026-06-10T00:36:20Z", "hours": 4.5428, "text": "Firstly I wrapped up the first step of this pipeline. I firstly changed Array Process to Alpha Process, and inside of it created functions for each step of that process making everything clean, professional, and modular. . After that I created a file called BetaProcess and restarted the Chemistry Checks there since there turned out to be MANY more steps to that process than what I had initially thought. Now what happens is firstly the Arrays we created in the Alpha Process are sent to deep seek to be put back together into molecular formulas. I this requires a new overly long prompt that details out all the steps the AI must take and chemistry rules and exceptions it must consider. I took some time in perfecting this prompt. After we get the reconstructed molecule we have to parse it out. Right now the LLM gives the molecule along with a whole response. I originally tried using Re to parse out the molecular formula. That didn’t work so then I had to format the LLM response to keep the answer at the end so I could just run normal string parsing to get the molecule. Then its shot off to the same LLM and prompt as the last devlog to find out how plausible the molecule is. . The challenges in this phase were making sure the deepsake model could put together even the hardest type of molecules so a big part of this was continuous testing and modifying of the prompt. . LLM’s are strange in how they always feel the need to have a 2 page explanation for every response. Because of that a bug challenge was figuring out how to parse out the information we want from each LLM response. . I was getting a headache looking at the outputs of this phase. Just words and number mushing together everywhere. So then I spent a lot of time formatting the output of this phase to make the information readable, understandable, and intuitive to follow."}, {"post_id": 4311, "ts": "2026-06-07T15:55:11Z", "hours": 3.3108, "text": "I started building the version 2 of Project Moonshine, a algorithm that’s meant to discover new crystals. This new engine takes a input of a reference material such as NH4H2PO4, and then breaks it into individual elements. It then systematically replaces every element with every element from the periodic table to generate THOUSANDS of potential new crystals. I got this idea from how real materials science discovery takes place. Scientists in a simulation mix and mash elements, using there extensive knowledge of chemistry to create new materials they think could work. Then atoms and elements are changed more to see what else can be created. . After we have our candidates I decided to first run initial screenings on the candidates to remove the ones that obviously won’t form stable crystals. I was initially going to test everything so we don’t lost any new crystals, but from version 1 I learned the enormous amount of time and compute that takes place in running high accuracy tests on these candidates (about 5 hours per test per molecule), and considering the fact I have over 10,000 CANDIDATES! and factoring in I want to finish this within the decade, I decided to run initial screenings. . I use the Qwen 2.5 model for plausibility analysis and deep seek to reconstruct the crystals from there array form that we created them in. When creating the candidates we break everything up into arrays, I thought the process of putting them back together would be as simple as counting the amount of times they appear in a array and then creating the empirical formula based on those subscripts of the elements. BUT NO. CHEMISTRY HAS 1000 RULES AND A 1000 MORE EXCEPTIONS IN MOLECULE FORMING. Instead of coding in every single one of these rules and exceptions , I decided to just use a AI model with strong reasoning. I am currently testing if this system for testing works. . Next I plan on improving the Chemistry rule set that these AI’s use so that I can make more accurate judgments about molecular forming and stability."}]...
|
Title: Moonshine by @kritik | Stardance
Devlogs:
Title: Moonshine by @kritik | Stardance
Devlogs:
I started building the version 2 of Project Moonshine, a algorithm that’s meant to discover new crystals. This new engine takes a input of a reference material such as NH4H2PO4, and then breaks it into individual elements. It then systematically replaces every element with every element from the periodic table to generate THOUSANDS of potential new crystals. I got this idea from how real materials science discovery takes place. Scientists in a simulation mix and mash elements, using there extensive knowledge of chemistry to create new materials they think could work. Then atoms and elements are changed more to see what else can be created. . After we have our candidates I decided to first run initial screenings on the candidates to remove the ones that obviously won’t form stable crystals. I was initially going to test everything so we don’t lost any new crystals, but from version 1 I learned the enormous amount of time and compute that takes place in running high accuracy tests on these candidates (about 5 hours per test per molecule), and considering the fact I have over 10,000 CANDIDATES! and factoring in I want to finish this within the decade, I decided to run initial screenings. . I use the Qwen 2.5 model for plausibility analysis and deep seek to reconstruct the crystals from there array form that we created them in. When creating the candidates we break everything up into arrays, I thought the process of putting them back together would be as simple as counting the amount of times they appear in a array and then creating the empirical formula based on those subscripts of the elements. BUT NO. CHEMISTRY HAS 1000 RULES AND A 1000 MORE EXCEPTIONS IN MOLECULE FORMING. Instead of coding in every single one of these rules and exceptions , I decided to just use a AI model with strong reasoning. I am currently testing if this system for testing works. . Next I plan on improving the Chemistry rule set that these AI’s use so that I can make more accurate judgments about molecular forming and stability.
Firstly I wrapped up the first step of this pipeline. I firstly changed Array Process to Alpha Process, and inside of it created functions for each step of that process making everything clean, professional, and modular. . After that I created a file called BetaProcess and restarted the Chemistry Checks there since there turned out to be MANY more steps to that process than what I had initially thought. Now what happens is firstly the Arrays we created in the Alpha Process are sent to deep seek to be put back together into molecular formulas. I this requires a new overly long prompt that details out all the steps the AI must take and chemistry rules and exceptions it must consider. I took some time in perfecting this prompt. After we get the reconstructed molecule we have to parse it out. Right now the LLM gives the molecule along with a whole response. I originally tried using Re to parse out the molecular formula. That didn’t work so then I had to format the LLM response to keep the answer at the end so I could just run normal string parsing to get the molecule. Then its shot off to the same LLM and prompt as the last devlog to find out how plausible the molecule is. . The challenges in this phase were making sure the deepsake model could put together even the hardest type of molecules so a big part of this was continuous testing and modifying of the prompt. . LLM’s are strange in how they always feel the need to have a 2 page explanation for every response. Because of that a bug challenge was figuring out how to parse out the information we want from each LLM response. . I was getting a headache looking at the outputs of this phase. Just words and number mushing together everywhere. So then I spent a lot of time formatting the output of this phase to make the information readable, understandable, and intuitive to follow.
I finished the Gamma Processing layer. This is the part of the file that takes in the formulas we created and screened in the Beta Processing Layer and then creates there structures and run a few initial validity tests on them. . First we start off with importing all the infinity stones of materials science. Then we get into our functions . First comes the Initial Super Gamma function. Ooooo fancyyy. No just kidding, I named everything so that I could tell which step of the process it came in just by reading the name. Initial tells me its the first and the Keyword super tells me its one of if not the first function to be run. Since keeping the order of every function run is super important for this to be built well this helps a lot. In the Initial Super Gamma Function we have a LLM, whos job is to take a look at the formula we created in the Beta Processing Layer and figure out what are the correct inputs to put into PyXtal for that formula. I will get into PyXtal in a bit . Next comes the SubGammaFunction. This function is nothing more than a overglorified string parser. It takes the output from the LLM, finds the key information we want, Dim, Group, Species, NumIons, and extracts them into variables we can input into PyXtal. Now all that seams straight forward right? So you can imagine my surprise when I was getting error after error in parsing the LLM response. I was so confused for some reason it could not extract the species from the response???? Yeah no it turned out I spelled species wrong in the function call. :) I know I make complaint jokes but its bugs, erros, and moments like that , that really make coding such a laugh, even those moments I really so enjoy. . Now back to the project! After parsing out all the information we can finally get to the interesting part 😈. CREATING AWESOME CRYSTAL STRUCTURES!!!!! PyXtal is a python tool that lets us randomly generate structures that don’t disobey fundamental laws of chemistry, such as Wyckoff positioning. The main challenge I had to overcome here was maintaining the structural group I had assigned to this crystal. PyXtal would be actively trying to create the best structure it thought was best but I wanted to preserve certain geometries to test since that is the most important thing in crystal creation . ANOTHER HUGE PROBLEM, I KEPT RUNNING OUT OF FREE CREDITS TO USE THE HUGGINGFACE AI MODELS. In the middle I tried to switch to Ollama locally hosted models I have before, but the remembered why I left them, THEY TAKE FOREVER. . After we create the PyXtal structures we run them through CHGNet to relax the structures, PyXtal SUCKS at creating low energy, high stability structures, its good at creating structures that don’t break certain rules such as Wyckoff positioning. After CHGNet relaxes the structure. It gives up the Stress values on the structure and the forces acting on the lattice of the crystal. We run 2 small loops to check each value and make sure its under 0.1 which is the value that is considered unstable for both metrics. If it passes the tests then its structure file is stored.
MOONSHINE PROJECT FULLY FINISHED. In this devlog I am going to share how I was able to finally complete the Moonshine algorithm into a system that can autonomously generate novel crystal structures. Firstly The Beta and Gamma processing layers were changed to use locally hosted ollama models for the AI reasoning capabilities. In the Gamma layer a few changes were made as well. After constant experimenting with different AI models and architectures for the pipeline this was the one that I landed on. In the Gamma layer Ollama uses Deepseek to generate parameters for PyXtal crystal structure generation. I learned through constant experimentation that the PyXtal library’s randomness for crystal structure generation is much worse than I thought initially. Initially I thought with 10-20 tries the right structure would be generated. But no. Now what happens is the pipeline takes the parameters generated by deepseek and creates 500 pyXtal crystal structures. This adds about 3 minutes to the compute time for each candidate coming in from the Beta Processing Layer, but increases total accuracy by about 40%. The reason this helps is because PyXtal doesn’t get the structure right the first time, so by creating 500 and then picking the lowest energy generation we get the best structure we can from PyXtal. The next change made was the CHGNet relaxation phase inside of the Gamma Processing Layer. Initially I was using a random combination of convergence values, and structure optimizers. I changed that so now there are two layers to the relaxation phase. The first phase is a rough, low level, coarse relaxation that creates a rough initial structure, this is done by keeping the convergence value at 0.01 and using the basic UnitCellFillter optimizer. In the more stricter final relaxation pass the convergence value is tightened to 0.001 and the more advanced FrechetCellFilter is used. This has two benefits. firstly after the first pass the structure can be checked for validity and discarded if it is invalid before moving onto more expensive relaxation, secondly the structure created by PyXtal is relaxed more gently, by first getting an initial form and then being tightened down to its final form instead of taking the initial broken PyXtal structure and immediately forcing it into a tight final structure. It’s kind of like working with clay when making pots. Next comes the new Delta Processing Layer. The delta processing layer tests the structures made by the Gamma Processing layer further by subjecting it to a suite of tests. Atomic overlap, composition, coordination number plusability, oxidation number plusability, and structure matching against the materials project is tested on the crystal. This is done five times per candidate in beta since gamma produces five structures per candidate. This effectively tests validity and novelty for each structure. Finally comes the new Epsilon Processing Layer. This layer analyzes the structures created to give a better understanding of what we created, along with creating slab structures for the unit cell structure. Slab structures are just unit cell structures repeated into 3d space. Unit cell analysis returns density, unit cell volume, lattice parameters, final space group symmetry, local atomic geometry, bond lengths, bond angles, and prototype classification. Then comes the slab analisis. First the slabs are created by pymatgen, the main library used in this entire project, and analyzed for the following: surface symmetry, polarity, surface normal vectors, scale factors, center of mass alignment, termination layer composition, candidate adsorption sites, and total surface area. Slabs are created along the three Miller indices; there are just numbers that tell how the crystal is sliced in 3d space in reference to the three axes, (1,0,0) (1,1,0) and (1,1,1). And that’s the algorithm I spent over a month on. Now I have to just leave it running for a while and see if it finds any new crystal materials.
Realizing the importance of A UI for this I had base 44 whip up a UI you can connect to the python backend once you download it so you can see the stats of the algorithm running
IMPORTANT NOTE MOONSHINE TAKES A FEW HOURS TO RUN FOR THE BETA AND GAMMA LAYERS, SO JUST CHECK THE TERMINAL THAT OPENS UP WITH THE UI TO MAKE SURE EVERYTHING IS WORKING AND JUST WAIT YOU CAN ALSO SEE IT WORKING THROUGH THAT TERMINAL OUTPUT JUST MAKE SURE TO DOWNLOAD OLLAMA AND THE TWO AI MODELES THAT GO WITH IT, GEMMA THREE AND DEEPSEAK R1 . . . . In this last devlog I am showing how I turned my python project into a file that anyone can download and use on there Mac device without fiddling with python files and github repos. And boy was that a adventure. Firstly I know quite a bit about building python projects and everthing to do with building projects inside VSCode. I know ABSOLUTLY NOTHING about turning that into something others can easily use. The battles I faught with learning about file paths and directories and temp folders and the whole bajazz was enough to make Roman warriors run. But nontheless with Claude as my sensie and enough caffine to send a todler to the moon I was able to figure it out and Im going to outline some of it now. Firstly this project is a multi script project where you run each stage (Alpha - Epsilon) and check the output for each and move onto the next stage and so on jsut becuase thats how I liked it best. Now to comuncate information through differtent scripts I used JSON’s. But when packaging a python project you must make it so that insted of just writting with open (, …) the filename cant just be a name, it has to be a whole path. Learning that fact and how to implement that was a strugle. Then came the strugle of makeing a master script. At the begining of my master script I was importing each python file for each stage. That mixed with not having a run function in each stage and using if “name” == “ main ” to run all the main code for each stage resulted in a kathuple amount of erros and problems such as scripts not running, multiple windows being created, and more. The last bug problem was how to package everything together. I tried command after command with nothing working, only to then learn of how I must move all my files into the Dict folder created when packaging in order to make suer everything works properly. Now I just have to put this in a github release and everyone can use the executable file I have made.
Ships:
I made a materials science engine meant to try and come up with candidates for novel materials with a high likleyhood of stability and validity for more advanced algorithms. The challenging part was integrating all the different tools being used, as well as perfectly tuning all tools to create accurate structures in as little time as possible. I am proud of the beautiful structures created by this algorithm. What to know to test this project is that its very unlikely a new material will be found on the first few tries, this has to be run for a while so start at the beta processing layer and run what is in the Alpha Arrays file. There is also lots of inaccuracies in this pipeline due to using off the self locally hosted LLM’s so you might have to run each layer a few times and not all candidates will be made....
|
1793325391.0409288
|
1793411791.0409288
|
|
3398
|
My first slack bot! by @Chalie | Stardance
|
Chalie
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Chalie | Stardance
|
1793263963.148855
|
1793868763.148855
|
|
3399
|
My awesome macropad! by @nathan_chan3000 | Stardan My awesome macropad! by @nathan_chan3000 | Stardance...
|
nathan_chan3000
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @nathan_chan3000 | Title: My awesome macropad! by @nathan_chan3000 | Stardance...
|
1793170113.094232
|
1793774913.094232
|
|
3400
|
Space Debris Tracking Platform by @anishissharma11 Space Debris Tracking Platform by @anishissharma11 | Stardance...
|
anishissharma11
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Space Debris Tracking Platform by @anishiss Title: Space Debris Tracking Platform by @anishissharma11 | Stardance...
|
1792748886.2465436
|
1793353686.2465436
|
|
3401
|
Clums-E by @PranavV | Stardance
|
PranavV
|
0
|
7.16
|
0
|
[]
|
[{"post_id": 3921, "ts": "2026 [{"post_id": 3921, "ts": "2026-06-07T01:11:08Z", "hours": 2.2339, "text": "Programming and Calibrating Servos: Servos don’t need calibration, but you need to ensure you know the right range of pulse which is why I made a reusable program that helps you find it and saves it for future reference. One cool thing I learned was command aliases in Linux. I was getting annoyed with doing git fetch & pull so I just made an alias “Refresh”"}, {"post_id": 2898, "ts": "2026-06-05T20:03:56Z", "hours": 2.8714, "text": "Powering Clums-E I shifted focus to the hardware background for Clums-E. I wired my 6V battery to the Mini PDP, ran it to the buck converter, and used a spliced Micro USB cable to link it to the Raspberry Pi. But the Pi stayed completely dead. After digging into it with Gemini and finding an article on cheap cables, I found the culprit. The cable I cut was a shoddy 3-wire line that used a thin layer of foil for the ground. It was completely useless for carrying power. I swapped it for a high-quality cable, and the Pi instantly booted up. With clean power finally flowing, I hooked up the Servo Driver, and it is officially up and talking to the Pi."}, {"post_id": 1250, "ts": "2026-06-03T03:15:43Z", "hours": 2.0506, "text": "Forward and inverse Kinematics: I started this project in Desmos by creating two polygons and calculated their relative coordinates based on a user-defined angle. After translating those relative coordinates to global ones, I finally had a working arm. At first, I had to manually adjust the angles to make the tip reach a target. I knew there had to be a better way. I wanted to just click a point and have the arm calculate the math on its own. That led me down the rabbit hole of Inverse Kinematics (IK). The Roadblock: After researching the math, I threw it into Desmos, but something was broken. The angle of joint 2 was completely off. After digging deeper, I realized my mistake. I was calculating the angle of segment 2 relative to segment 1, but the renderer actually needed the angle relative to the origin. The Breakthrough The math did not click for me until I imagined a person walking up a hill. If you are climbing a slope and reach a peak, you need to know the exact change in your angle to keep moving along the new path. To solve this, I extended the first segment line and found the supplementary angle to my original calculation. Once I applied that shift, the arm snapped perfectly into place. Now, the arm seamlessly calculates its own angles and reaches the goal point automatically. I then implemented the same Math into my Python project"}]...
|
Title: Clums-E by @PranavV | Stardance
Devlogs:
F Title: Clums-E by @PranavV | Stardance
Devlogs:
Forward and inverse Kinematics: I started this project in Desmos by creating two polygons and calculated their relative coordinates based on a user-defined angle. After translating those relative coordinates to global ones, I finally had a working arm. At first, I had to manually adjust the angles to make the tip reach a target. I knew there had to be a better way. I wanted to just click a point and have the arm calculate the math on its own. That led me down the rabbit hole of Inverse Kinematics (IK). The Roadblock: After researching the math, I threw it into Desmos, but something was broken. The angle of joint 2 was completely off. After digging deeper, I realized my mistake. I was calculating the angle of segment 2 relative to segment 1, but the renderer actually needed the angle relative to the origin. The Breakthrough The math did not click for me until I imagined a person walking up a hill. If you are climbing a slope and reach a peak, you need to know the exact change in your angle to keep moving along the new path. To solve this, I extended the first segment line and found the supplementary angle to my original calculation. Once I applied that shift, the arm snapped perfectly into place. Now, the arm seamlessly calculates its own angles and reaches the goal point automatically. I then implemented the same Math into my Python project
Powering Clums-E I shifted focus to the hardware background for Clums-E. I wired my 6V battery to the Mini PDP, ran it to the buck converter, and used a spliced Micro USB cable to link it to the Raspberry Pi. But the Pi stayed completely dead. After digging into it with Gemini and finding an article on cheap cables, I found the culprit. The cable I cut was a shoddy 3-wire line that used a thin layer of foil for the ground. It was completely useless for carrying power. I swapped it for a high-quality cable, and the Pi instantly booted up. With clean power finally flowing, I hooked up the Servo Driver, and it is officially up and talking to the Pi.
Programming and Calibrating Servos: Servos don’t need calibration, but you need to ensure you know the right range of pulse which is why I made a reusable program that helps you find it and saves it for future reference. One cool thing I learned was command aliases in Linux. I was getting annoyed with doing git fetch & pull so I just made an alias “Refresh”...
|
1793184644.838382
|
1793789444.838382
|
|
3402
|
Balloon Payload by @trexhaydor | Stardance
|
trexhaydor
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Balloon Payload by @trexhaydor | Stardance
|
1793418729.229404
|
1794023529.229404
|
|
3403
|
Spider quadruped robot by @lillia | Stardance
|
lillia
|
0
|
3.45
|
0
|
[]
|
[{"post_id": 1174, "ts": "2026 [{"post_id": 1174, "ts": "2026-06-03T01:08:19Z", "hours": 2.1064, "text": "Finalizing proper servo measurements for 3d print!"}, {"post_id": 578, "ts": "2026-06-02T02:20:33Z", "hours": 1.3442, "text": "I’m working on my CAD for the spider robot base (this took longer than 1h 20m but I never logged it)"}]...
|
Title: Spider quadruped robot by @lillia | Stardan Title: Spider quadruped robot by @lillia | Stardance
Devlogs:
I’m working on my CAD for the spider robot base (this took longer than 1h 20m but I never logged it)
Finalizing proper servo measurements for 3d print!...
|
1792795657.853059
|
1793400457.853059
|
|
3404
|
My awesome macropad! by @peachcobble | Stardance
|
peachcobble
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @peachcobble | Star Title: My awesome macropad! by @peachcobble | Stardance...
|
1793299760.906868
|
1793904560.906868
|
|
3405
|
Untitled project by @SC | Stardance
|
SC
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @SC | Stardance
|
1792806695.8025434
|
1793411495.8025434
|
|
3406
|
My awesome macropad! by @haz | Stardance
|
haz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @haz | Stardance
|
1793296293.6159875
|
1793901093.6159875
|
|
3407
|
Ackshually🤓☝️ by @Mia | Stardance
|
Mia
|
0
|
0.41
|
0
|
[]
|
[{"post_id": 908, "ts": "2026- [{"post_id": 908, "ts": "2026-06-02T17:21:30Z", "hours": 0.4142, "text": "IT’S ALIVE!! I did some boilerplate Slack Bolt setup in Python, making sure I can have it respond to messages. Next up is a “magic 8 ball” feature that has a tendency to answer in the affirmative!"}]...
|
Title: Ackshually🤓☝️ by @Mia | Stardance
Devlogs: Title: Ackshually🤓☝️ by @Mia | Stardance
Devlogs:
IT’S ALIVE!! I did some boilerplate Slack Bolt setup in Python, making sure I can have it respond to messages. Next up is a “magic 8 ball” feature that has a tendency to answer in the affirmative!...
|
1793202799.2404985
|
1793807599.2404985
|
|
3408
|
Project AETA (Algae & Environmental Telemetry Project AETA (Algae & Environmental Telemetry Architecture) by @dennis | Stardance...
|
dennis
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Project AETA (Algae & Environmental Tel Title: Project AETA (Algae & Environmental Telemetry Architecture) by @dennis | Stardance...
|
1793303428.0088766
|
1793908228.0088766
|
|
3409
|
Bongr by @Voxi0 | Stardance
|
Voxi0
|
0
|
9.46
|
0
|
[]
|
[{"post_id": 1515, "ts": "2026 [{"post_id": 1515, "ts": "2026-06-03T16:20:53Z", "hours": 2.5128, "text": "Added a scoreboard and scoring system and all. I figured out how to make use of the resources system that Bevy makes use of to keep track of the player’s scores and be able to update/access it in functions. I also figured out that Avian offers a Sensor property which turns a collider into just something used for detection instead of having any physical stuff. Since the players are meant to score by bouncing the ball back and making it hit the wall behind the opponent, I added the Sensor property to both the left and right walls so the ball doesn’t collide or anything with them making it look like there aren’t even any walls there. Then it’s just a matter of adding a .observe() to handle collision events so we can update the scores properly depending on which wall the ball hits. It took me a while to figure out how to set up the scoreboard and get it looking the way I want but yeah it’s there now and is updated everytime someone scores instead of constantly updating it or something. Now I need to make the ball respawns after either player scores because right now, it just leaves the screen and never comes back."}, {"post_id": 1128, "ts": "2026-06-02T23:25:28Z", "hours": 0.915, "text": "I added a simple ball and just for fun, I also introduced a full on proper 2D physics engine called Avian2D instead of me manually calculating and handling collisions and such. And while it is probably (pretty sure absolutely) overkill, it’s genuinely more satisfying to play around with. I’ll organize and move stuff around a bit before adding in a scoreboard and figuring out how to set up a scoring system. After that, I’ll just polish up my project to be more nice and enjoyable since the basics of Pong are pretty much already taken care of anyways. So stuff like a main menu and using actual proper textures/images instead of just shapes with a plain color and such you know."}, {"post_id": 1049, "ts": "2026-06-02T21:05:08Z", "hours": 6.0333, "text": "Spent a long, long while trying to understand Bevy and it’s ECS implementation along with a bunch of Rust syntax I have not yet encountered. While I still do not understand everything entirely, I have a decent grasp on the basics of Bevy and how it functions and handles stuff using the ECS pattern. I know enough to be able to do some basic things like create entities and handle input and draw some stuff and such. After playing around for a while, I finally took the time to go ahead and wipe everything to start fresh. Created a simple Nix flake to define my build/dev environment and set up a basic Rust project using Bevy before creating the Paddles and adding movement and such to them. I took some time to organize everything and sue constants/variables in various places as well to ensure that I’m not overusing magic numbers in my project and to provide a sort of control center to change the looks/behavior of the entire game easily. Now it’s time to create the ball…"}]...
|
Title: Bongr by @Voxi0 | Stardance
Devlogs:
Spent Title: Bongr by @Voxi0 | Stardance
Devlogs:
Spent a long, long while trying to understand Bevy and it’s ECS implementation along with a bunch of Rust syntax I have not yet encountered. While I still do not understand everything entirely, I have a decent grasp on the basics of Bevy and how it functions and handles stuff using the ECS pattern. I know enough to be able to do some basic things like create entities and handle input and draw some stuff and such. After playing around for a while, I finally took the time to go ahead and wipe everything to start fresh. Created a simple Nix flake to define my build/dev environment and set up a basic Rust project using Bevy before creating the Paddles and adding movement and such to them. I took some time to organize everything and sue constants/variables in various places as well to ensure that I’m not overusing magic numbers in my project and to provide a sort of control center to change the looks/behavior of the entire game easily. Now it’s time to create the ball…
I added a simple ball and just for fun, I also introduced a full on proper 2D physics engine called Avian2D instead of me manually calculating and handling collisions and such. And while it is probably (pretty sure absolutely) overkill, it’s genuinely more satisfying to play around with. I’ll organize and move stuff around a bit before adding in a scoreboard and figuring out how to set up a scoring system. After that, I’ll just polish up my project to be more nice and enjoyable since the basics of Pong are pretty much already taken care of anyways. So stuff like a main menu and using actual proper textures/images instead of just shapes with a plain color and such you know.
Added a scoreboard and scoring system and all. I figured out how to make use of the resources system that Bevy makes use of to keep track of the player’s scores and be able to update/access it in functions. I also figured out that Avian offers a Sensor property which turns a collider into just something used for detection instead of having any physical stuff. Since the players are meant to score by bouncing the ball back and making it hit the wall behind the opponent, I added the Sensor property to both the left and right walls so the ball doesn’t collide or anything with them making it look like there aren’t even any walls there. Then it’s just a matter of adding a .observe() to handle collision events so we can update the scores properly depending on which wall the ball hits. It took me a while to figure out how to set up the scoreboard and get it looking the way I want but yeah it’s there now and is updated everytime someone scores instead of constantly updating it or something. Now I need to make the ball respawns after either player scores because right now, it just leaves the screen and never comes back....
|
1793170370.4939368
|
1793775170.4939368
|
|
3410
|
3D Horror Survival by @EMM27 | Stardance
|
EMM27
|
0
|
1.89
|
0
|
[]
|
[{"post_id": 504, "ts": "2026- [{"post_id": 504, "ts": "2026-06-01T23:52:46Z", "hours": 1.8933, "text": "This project is still a work in progress (from Macondo), but this is my first Devlog here. Today I have made a main menu shop button but I will show my previous screenshots before I did that. I will show it in my next devlog, this will just be a sort of introduction."}]...
|
Title: 3D Horror Survival by @EMM27 | Stardance
D Title: 3D Horror Survival by @EMM27 | Stardance
Devlogs:
This project is still a work in progress (from Macondo), but this is my first Devlog here. Today I have made a main menu shop button but I will show my previous screenshots before I did that. I will show it in my next devlog, this will just be a sort of introduction....
|
1793184905.107878
|
1793789705.107878
|
|
3411
|
Untitled by @shaurya_singh | Stardance
|
shaurya_singh
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @shaurya_singh | Stardance
|
1793155672.4708042
|
1793760472.4708042
|
|
3412
|
My awesome macropad! by @Sana | Stardance
|
Sana
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @Sana | Stardance
|
1792756570.811534
|
1793361370.811534
|
|
3413
|
My first slack bot! by @shasthav | Stardance
|
shasthav
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @shasthav | Stardanc Title: My first slack bot! by @shasthav | Stardance...
|
1792803088.9599555
|
1793407888.9599555
|
|
3414
|
Untitled by @ishaank | Stardance
|
ishaank
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @ishaank | Stardance
|
1793278317.0829034
|
1793883117.0829034
|
|
3415
|
Personal Website by @ananya_iyer | Stardance
|
ananya_iyer
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Personal Website by @ananya_iyer | Stardanc Title: Personal Website by @ananya_iyer | Stardance...
|
1792774222.3222713
|
1793379022.3222713
|
|
3416
|
My first slack bot! by @Sharad | Stardance
|
Sharad
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Sharad | Stardance
|
1792810062.1816266
|
1793414862.1816266
|
|
3417
|
Untitled project by @Anvid | Stardance
|
Anvid
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Anvid | Stardance
|
1793184597.2363715
|
1793789397.2363715
|
|
3418
|
Mission:Earth by @Sritha | Stardance
|
Sritha
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Mission:Earth by @Sritha | Stardance
|
1793145329.7939699
|
1793750129.7939699
|
|
3419
|
My first slack bot! by @hadiya | Stardance
|
hadiya
|
1
|
1.0
|
0
|
[{"ship_num": 1, "ts": "2026-0 [{"ship_num": 1, "ts": "2026-06-03T19:22:00Z", "hours": 1.0, "multiplier": null, "payout": 0, "blessing": "neutral", "text": "I’m a beginner ;) I built a Slack bot that responds to slash commands using Node.js and Slack Bot. It includes multiple fun and useful commands like: /dsb-ping → checks bot latency /dsb-catfact → returns random cat facts /dsb-joke → returns random jokes the bot runs 24/7 on a server using systemd, so it stays online even when my laptop is off. Challenges! I had issues deploying the bot so it runs continuously on a server but managed to figure it out. Tried adding new slash commands but kept running into errors ;( I am proud that I successfully built a fully working Slack bot that integrates APIs and runs continuously on a server :D I also improved my debugging skills and learned how to deploy Node.js applications properly using systemd.", "repo": "https://github.com/hadiiye/slack-bot", "demo": "https://github.com/hadiiye/slack-bot/blob/main/README.md"}]...
|
[{"post_id": 1607, "ts": "2026 [{"post_id": 1607, "ts": "2026-06-03T18:59:17Z", "hours": 0.5233, "text": "having certain issues on the new slack commands :0"}, {"post_id": 1016, "ts": "2026-06-02T20:08:52Z", "hours": 0.3108, "text": "Very first slack bot :D"}]...
|
Title: My first slack bot! by @hadiya | Stardance
Title: My first slack bot! by @hadiya | Stardance
Devlogs:
Very first slack bot :D
having certain issues on the new slack commands :0
Ships:
I’m a beginner ;) I built a Slack bot that responds to slash commands using Node.js and Slack Bot. It includes multiple fun and useful commands like: /dsb-ping → checks bot latency /dsb-catfact → returns random cat facts /dsb-joke → returns random jokes the bot runs 24/7 on a server using systemd, so it stays online even when my laptop is off. Challenges! I had issues deploying the bot so it runs continuously on a server but managed to figure it out. Tried adding new slash commands but kept running into errors ;( I am proud that I successfully built a fully working Slack bot that integrates APIs and runs continuously on a server :D I also improved my debugging skills and learned how to deploy Node.js applications properly using systemd....
|
1793267589.7317932
|
1793353989.7317932
|
|
3420
|
The...INFI_PC! by @Bobert3D | Stardance
|
Bobert3D
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: The...INFI_PC! by @Bobert3D | Stardance
|
1792932579.876642
|
1793796579.876642
|
|
3421
|
Untitled project by @Reacher9046 | Stardance
|
Reacher9046
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Reacher9046 | Stardanc Title: Untitled project by @Reacher9046 | Stardance...
|
1792738438.5896122
|
1793343238.5896122
|
|
3422
|
Grow by @JP | Stardance
|
JP
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Grow by @JP | Stardance
|
1792623328.843666
|
1793487328.843666
|
|
3423
|
Untitled by @ishowspeed | Stardance
|
ishowspeed
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @ishowspeed | Stardance
|
1792947063.048485
|
1793811063.048485
|
|
3424
|
My awesome macropad! by @choudharyaditya974 | Star My awesome macropad! by @choudharyaditya974 | Stardance...
|
choudharyaditya974
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @choudharyaditya974 Title: My awesome macropad! by @choudharyaditya974 | Stardance...
|
1793469205.4499574
|
1794074005.4499574
|
|
3425
|
rsynth by @rwrv | Stardance
|
rwrv
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: rsynth by @rwrv | Stardance
|
1793299903.8876967
|
1793904703.8876967
|
|
3426
|
Untitled by @Naytik | Stardance
|
Naytik
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Naytik | Stardance
|
1792799542.4094603
|
1793404342.4094603
|
|
3427
|
Untitled project by @Tyrichyrich | Stardance
|
Tyrichyrich
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Tyrichyrich | Stardanc Title: Untitled project by @Tyrichyrich | Stardance...
|
1793173682.2165387
|
1793778482.2165387
|
|
3428
|
The sustail by @bellw | Stardance
|
bellw
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: The sustail by @bellw | Stardance
|
1792781537.632716
|
1793386337.632716
|
|
3429
|
idk by @SillySilicon | Stardance
|
SillySilicon
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: idk by @SillySilicon | Stardance
|
1792778080.191564
|
1793382880.191564
|
|
3430
|
My awesome macropad! by @liashley250 | Stardance
|
liashley250
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My awesome macropad! by @liashley250 | Star Title: My awesome macropad! by @liashley250 | Stardance...
|
1793267685.4026577
|
1793872485.4026577
|
|
3431
|
My first slack bot! by @julianas82311 | Stardance
|
julianas82311
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @julianas82311 | Sta Title: My first slack bot! by @julianas82311 | Stardance...
|
1793206151.537552
|
1793810951.537552
|