|
11383
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826466.3522418
|
1792690466.3522418
|
|
11789
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826466.1784422
|
1792690466.1784422
|
|
27572
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826465.9841971
|
1792690465.9841971
|
|
32597
|
Fight4Code by @ice__fizz | Stardance
|
ice__fizz
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Fight4Code by @ice__fizz | Stardance
|
1791826465.8382638
|
1792690465.8382638
|
|
7342
|
My first slack bot! by @summywummy | Stardance
|
summywummy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @summywummy | Starda Title: My first slack bot! by @summywummy | Stardance...
|
1791826465.6007159
|
1792690465.6007159
|
|
39590
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826465.3987198
|
1792690465.3987198
|
|
28729
|
Competition website by @LinuxDino | Stardance
|
LinuxDino
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Competition website by @LinuxDino | Stardan Title: Competition website by @LinuxDino | Stardance...
|
1791826465.23056
|
1792690465.23056
|
|
12929
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826465.1998525
|
1792690465.1998525
|
|
39752
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826465.1967115
|
1792690465.1967115
|
|
40245
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826465.193595
|
1792690465.193595
|
|
34196
|
Open Aero by @Liam303 | Stardance
|
Liam303
|
0
|
36.0
|
0
|
[]
|
[{"post_id": 28096, "ts": "202 [{"post_id": 28096, "ts": "2026-07-14T04:25:04Z", "hours": 4.0, "text": "New Beginnings: After the completion and submission of my last project (and alot of sleep) I have begun my new project. This time I wanted to test my abilities so I’m making an easy to use aero sim. My plan for uni is engineering aerodynamics so I’m taking this chance to learn as much about it as possible by designing my own, I have seen plenty of cool cad designs on Stardance that could be tested in one. I’m going to try take this project a lot slower and just get it right. Today I finally applied physics equations outside of school, I used the equation for drag, (F_d = 1/2pv^2 * C_d *A). My plan is to at first just create a simple 2d simulator, nothing complex just so I can test the basic functions."}, {"post_id": 28219, "ts": "2026-07-14T11:16:31Z", "hours": 6.0, "text": "I’m not a big UI connoisseur and not very original so I used the same UI library as from Open Wall because I know how to use it, don’t worry I’ll change it in the future. And for all those waiting I’ve revolutionized aerodynamic simulation, I can calculate and simulate the aerodynamics of a… circle. Yeah, not the most exiting, but I’m pretty sure that part of it is working. I couldn’t get the drag force telemetry graph working properly, but that’s not a huge deal right now, but also found some distortion on the simulation. Its a problem with my graph ability more then my simulation ability, as much as it may surprised you all I’m not the best coder of all time, but for now I’m happy with how its working and I’m going to try start making it 3d next time."}, {"post_id": 28780, "ts": "2026-07-15T08:44:45Z", "hours": 5.0, "text": "Can’t say I’m surprised, if you want to make a complex aerodynamics software your bound to crash it a couple of times. Fixing errors is boring so I’ve moved onto making the 3d part of the software, I’m sure there’s a simple reason behind the crash but I don’t know what it is yet so time to go back to code cut to intense coding montage"}, {"post_id": 29286, "ts": "2026-07-16T03:09:06Z", "hours": 4.0, "text": "I hit an absolute gold mine. So my code so far has been based on a ui library for python, which is fine for two and graph plotting but lingering in the back of my mind has been this fear of how I’m going to actually set up the 3d simulation part of my software, kind of important for a 3d aerodynamics simulator. That’s when I came across pyvista, which is a library made for my exact purpose, it means I have to remake most of my code, which I already knew I would need to do, but I’m so exited to see stuff start working, I’m still far of actually finishing the 3d ‘engine’ but I feel more motivated then ever"}, {"post_id": 29443, "ts": "2026-07-16T12:04:12Z", "hours": 7.0, "text": "I’m not narcissistic I just think I’m the best coder to have ever existed on earth, I’ve been able to make my own 3d engine and all I’ve had to do is use somebody else’s library with somebody else’s example code with a lot of tutorials and a huge amount of errors most of which were a result of misspellings. So far the 3d viewers works, it doesn’t do anything yet but the basics are there, I’ve rewritten all of my code from the ground up so I haven’t started on the complex math’s stuff (not exited for that), progress is coming along slowly but shortly"}, {"post_id": 29974, "ts": "2026-07-17T05:59:47Z", "hours": 5.0, "text": "I’m improving, soon I will be able to calculate and visualize the aerodynamics of a… sphere. Yeah its not the most interesting dev log ever, I’m working on turn the calculations into visual representations, this involves particle collisions and making the engine more efficient. The main issues are around the collisions, there’s a surprising lack of errors rather its just the ‘air’ particles fazing through the mech. No interesting photos this time, more updates to come soon."}, {"post_id": 30102, "ts": "2026-07-17T12:40:27Z", "hours": 5.0, "text": "It’s works. I am so unbelievably surprised that it works, yes it might be like 5 frames a second but it works. There’s not much to say in this dev logs other than the fact that I am literally jumping with joy. Not even kidding just I was about to sit down and write this develop about how nothing was working, I tried one fix and it works. To many of you python fanatics this might not seem like a big achievement but to me this is one of my biggest coding accomplishments ever. I am more energetic then ever to finish this project."}]...
|
Title: Open Aero by @Liam303 | Stardance
Devlogs: Title: Open Aero by @Liam303 | Stardance
Devlogs:
New Beginnings: After the completion and submission of my last project (and alot of sleep) I have begun my new project. This time I wanted to test my abilities so I’m making an easy to use aero sim. My plan for uni is engineering aerodynamics so I’m taking this chance to learn as much about it as possible by designing my own, I have seen plenty of cool cad designs on Stardance that could be tested in one. I’m going to try take this project a lot slower and just get it right. Today I finally applied physics equations outside of school, I used the equation for drag, (F_d = 1/2pv^2 * C_d *A). My plan is to at first just create a simple 2d simulator, nothing complex just so I can test the basic functions.
I’m not a big UI connoisseur and not very original so I used the same UI library as from Open Wall because I know how to use it, don’t worry I’ll change it in the future. And for all those waiting I’ve revolutionized aerodynamic simulation, I can calculate and simulate the aerodynamics of a… circle. Yeah, not the most exiting, but I’m pretty sure that part of it is working. I couldn’t get the drag force telemetry graph working properly, but that’s not a huge deal right now, but also found some distortion on the simulation. Its a problem with my graph ability more then my simulation ability, as much as it may surprised you all I’m not the best coder of all time, but for now I’m happy with how its working and I’m going to try start making it 3d next time.
Can’t say I’m surprised, if you want to make a complex aerodynamics software your bound to crash it a couple of times. Fixing errors is boring so I’ve moved onto making the 3d part of the software, I’m sure there’s a simple reason behind the crash but I don’t know what it is yet so time to go back to code cut to intense coding montage
I hit an absolute gold mine. So my code so far has been based on a ui library for python, which is fine for two and graph plotting but lingering in the back of my mind has been this fear of how I’m going to actually set up the 3d simulation part of my software, kind of important for a 3d aerodynamics simulator. That’s when I came across pyvista, which is a library made for my exact purpose, it means I have to remake most of my code, which I already knew I would need to do, but I’m so exited to see stuff start working, I’m still far of actually finishing the 3d ‘engine’ but I feel more motivated then ever
I’m not narcissistic I just think I’m the best coder to have ever existed on earth, I’ve been able to make my own 3d engine and all I’ve had to do is use somebody else’s library with somebody else’s example code with a lot of tutorials and a huge amount of errors most of which were a result of misspellings. So far the 3d viewers works, it doesn’t do anything yet but the basics are there, I’ve rewritten all of my code from the ground up so I haven’t started on the complex math’s stuff (not exited for that), progress is coming along slowly but shortly
I’m improving, soon I will be able to calculate and visualize the aerodynamics of a… sphere. Yeah its not the most interesting dev log ever, I’m working on turn the calculations into visual representations, this involves particle collisions and making the engine more efficient. The main issues are around the collisions, there’s a surprising lack of errors rather its just the ‘air’ particles fazing through the mech. No interesting photos this time, more updates to come soon.
It’s works. I am so unbelievably surprised that it works, yes it might be like 5 frames a second but it works. There’s not much to say in this dev logs other than the fact that I am literally jumping with joy. Not even kidding just I was about to sit down and write this develop about how nothing was working, I tried one fix and it works. To many of you python fanatics this might not seem like a big achievement but to me this is one of my biggest coding accomplishments ever. I am more energetic then ever to finish this project....
|
1791826465.1902275
|
1792690465.1902275
|
|
11667
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826465.1873212
|
1792690465.1873212
|
|
10199
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826465.1841292
|
1792690465.1841292
|
|
40523
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826465.1809814
|
1792690465.1809814
|
|
477
|
Untitled project by @Googentity | Stardance
|
Googentity
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled project by @Googentity | Stardance
|
1791826465.178216
|
1792690465.178216
|
|
14134
|
My very own WebOS by @krishiv_vyas | Stardance
|
krishiv_vyas
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @krishiv_vyas | Starda Title: My very own WebOS by @krishiv_vyas | Stardance...
|
1791826465.1749587
|
1792690465.1749587
|
|
12424
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826463.3386838
|
1792690463.3386838
|
|
48651
|
Polaris-Custom Launchpad by @Sreeni | Stardance
|
Sreeni
|
0
|
1.9
|
0
|
[]
|
[{"post_id": 48549, "ts": "202 [{"post_id": 48549, "ts": "2026-08-16T23:59:13Z", "hours": 1.9022, "text": "So this is the launchpad part of my tvc rocket project, I first began by looking through some versions that other people had made like bps space, and t-zero systems and looked through some actual launchpads used on rockets. With an overall idea I then planned what needed for the launch pad 1.Flame trench, made of steel or aluminium whichever I can find for cheap 2.Igniter system 3.Servos for launch pad clamps 4.lighting(WS2812 RGB LED Breakout) 5.PCB to control all of this in one for the servos im going to use mg90s servos, I’m still working on the bottom clamp that will hold the bottom of the rocket, but I’m not sure if I really need it?, Ithink it’d be simpler to just use a basic stand but we will see. Other than that I’m going to work on the pcb and finish up the cad model"}]...
|
Title: Polaris-Custom Launchpad by @Sreeni | Stard Title: Polaris-Custom Launchpad by @Sreeni | Stardance
Devlogs:
So this is the launchpad part of my tvc rocket project, I first began by looking through some versions that other people had made like bps space, and t-zero systems and looked through some actual launchpads used on rockets. With an overall idea I then planned what needed for the launch pad 1.Flame trench, made of steel or aluminium whichever I can find for cheap 2.Igniter system 3.Servos for launch pad clamps 4.lighting(WS2812 RGB LED Breakout) 5.PCB to control all of this in one for the servos im going to use mg90s servos, I’m still working on the bottom clamp that will hold the bottom of the rocket, but I’m not sure if I really need it?, Ithink it’d be simpler to just use a basic stand but we will see. Other than that I’m going to work on the pcb and finish up the cad model...
|
1791826463.131596
|
1792690463.131596
|
|
16653
|
Untitled by @notishi28 | Stardance
|
notishi28
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @notishi28 | Stardance
|
1791826462.9579773
|
1792690462.9579773
|
|
38939
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826462.779389
|
1792690462.779389
|
|
3129
|
My first slack bot! by @Hima_Shreyas_Nagumalla | S My first slack bot! by @Hima_Shreyas_Nagumalla | Stardance...
|
Hima_Shreyas_Nagumalla
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My first slack bot! by @Hima_Shreyas_Naguma Title: My first slack bot! by @Hima_Shreyas_Nagumalla | Stardance...
|
1791826462.5755098
|
1792690462.5755098
|
|
45088
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826462.4071465
|
1792690462.4071465
|
|
45055
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826462.2053523
|
1792690462.2053523
|
|
45054
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826462.022571
|
1792690462.022571
|
|
12943
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826461.8194368
|
1792690461.8194368
|
|
40614
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826461.6370502
|
1792690461.6370502
|
|
33518
|
Apollo Web Proxy by @fierce | Stardance
|
fierce
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Apollo Web Proxy by @fierce | Stardance
|
1791826461.4446795
|
1792690461.4446795
|
|
39105
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826461.274269
|
1792690461.274269
|
|
38976
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826461.0778494
|
1792690461.0778494
|
|
29586
|
G.R.I.D by @urged-st | Stardance
|
urged-st
|
0
|
6.91
|
0
|
[]
|
[{"post_id": 30814, "ts": "202 [{"post_id": 30814, "ts": "2026-07-18T18:57:25Z", "hours": 5.4217, "text": "GRID - Double Well HELL Most of this session went into one bug, and it’s a genuinely annoying one to reason about, which is why it ate the time. Added the second mass early on, that part was quick, just refactored mass into a masses array and summed each one’s pull vector. Linear superposition, same as before. Problem showed up the second I dragged the two masses toward each other. The mesh was folding, points crossing lines they shouldn’t. My first assumption was the per-mass clamp had a bug, so I spent a while re-checking schwarzschildPull in isolation, it was fine, each mass on its own respects its horizon exactly like build 2. Took embarrassingly long to actually accept that the bug wasn’t in either clamp, it was in the fact there wasn’t a clamp on the SUM. Each mass says “don’t let this point cross my horizon” independently, but if both are pulling the same point in roughly the same direction, the two allowed pulls can add up to more than either alone would permit. Obvious in hindsight. Tried a couple of wrong fixes before the right one. First attempt was averaging the two pulls instead of summing, which just made single-mass behaviour weaker for no reason and didn’t even fix the overlap case properly. Also considered some kind of smooth blend between the two wells (metaball-style), which would’ve looked nicer but is a much bigger rabbit hole than 5 hours allows, parked that idea for later. What actually worked was tracking the tightest safe margin (distance to nearest horizon) across all masses while summing, then if the combined pull vector exceeds that margin, scale the whole vector down before applying it. So the constraint moved from “per mass” to “per point, against whichever horizon is closest.” One extra variable, safeMargin , and a scale-down at the end. The fix itself is maybe four lines, finding the actual shape of the problem was the other 4+ hours. Worth saying clearly, this doesn’t make two overlapping wells physically correct. Real GR still doesn’t superpose like this. What it does is stop the visualisation showing impossible geometry, the mesh degrades gracefully at the boundary instead of folding through itself. Hopefully the next session is calmer than ts bro it took way too long"}, {"post_id": 26233, "ts": "2026-07-10T22:00:09Z", "hours": 1.49, "text": "GRID Begins Third simulator in the lineup, and this one’s a spacetime mesh, so instead of watching an object move through space you’re watching space bend around it. Started with a plain grid of points, then had to figure out how to actually pull them toward a mass without it looking like noise. Went with an inverse square-ish falloff (not GR accurate, more of a stylised well for now) and it clicked visually with barely any tuning. The annoying part was stopping the mesh folding back through the mass itself when you drag it in close. Lines were crossing over each other and it looked completely broken. Fixed it by clamping the pull so it eases off the closer you get instead of spiking, simple fix once I saw what was actually happening. Kept tonight deliberately small, one grid, one draggable mass, nothing else. Wanted to prove the warp looks proper before building anything on top of it (that went well for g-lens lmao) Next up: strength slider and a reset button, then a second mass to see how two wells interact with each other."}]...
|
Title: G.R.I.D by @urged-st | Stardance
Devlogs:
Title: G.R.I.D by @urged-st | Stardance
Devlogs:
GRID Begins Third simulator in the lineup, and this one’s a spacetime mesh, so instead of watching an object move through space you’re watching space bend around it. Started with a plain grid of points, then had to figure out how to actually pull them toward a mass without it looking like noise. Went with an inverse square-ish falloff (not GR accurate, more of a stylised well for now) and it clicked visually with barely any tuning. The annoying part was stopping the mesh folding back through the mass itself when you drag it in close. Lines were crossing over each other and it looked completely broken. Fixed it by clamping the pull so it eases off the closer you get instead of spiking, simple fix once I saw what was actually happening. Kept tonight deliberately small, one grid, one draggable mass, nothing else. Wanted to prove the warp looks proper before building anything on top of it (that went well for g-lens lmao) Next up: strength slider and a reset button, then a second mass to see how two wells interact with each other.
GRID - Double Well HELL Most of this session went into one bug, and it’s a genuinely annoying one to reason about, which is why it ate the time. Added the second mass early on, that part was quick, just refactored mass into a masses array and summed each one’s pull vector. Linear superposition, same as before. Problem showed up the second I dragged the two masses toward each other. The mesh was folding, points crossing lines they shouldn’t. My first assumption was the per-mass clamp had a bug, so I spent a while re-checking schwarzschildPull in isolation, it was fine, each mass on its own respects its horizon exactly like build 2. Took embarrassingly long to actually accept that the bug wasn’t in either clamp, it was in the fact there wasn’t a clamp on the SUM. Each mass says “don’t let this point cross my horizon” independently, but if both are pulling the same point in roughly the same direction, the two allowed pulls can add up to more than either alone would permit. Obvious in hindsight. Tried a couple of wrong fixes before the right one. First attempt was averaging the two pulls instead of summing, which just made single-mass behaviour weaker for no reason and didn’t even fix the overlap case properly. Also considered some kind of smooth blend between the two wells (metaball-style), which would’ve looked nicer but is a much bigger rabbit hole than 5 hours allows, parked that idea for later. What actually worked was tracking the tightest safe margin (distance to nearest horizon) across all masses while summing, then if the combined pull vector exceeds that margin, scale the whole vector down before applying it. So the constraint moved from “per mass” to “per point, against whichever horizon is closest.” One extra variable, safeMargin , and a scale-down at the end. The fix itself is maybe four lines, finding the actual shape of the problem was the other 4+ hours. Worth saying clearly, this doesn’t make two overlapping wells physically correct. Real GR still doesn’t superpose like this. What it does is stop the visualisation showing impossible geometry, the mesh degrades gracefully at the boundary instead of folding through itself. Hopefully the next session is calmer than ts bro it took way too long...
|
1791826460.8740525
|
1792690460.8740525
|
|
3496
|
Python Password checker by @samzy | Stardance
|
samzy
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Python Password checker by @samzy | Stardan Title: Python Password checker by @samzy | Stardance...
|
1791826460.6827393
|
1792690460.6827393
|
|
38775
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826460.5109675
|
1792690460.5109675
|
|
11402
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826460.32214
|
1792690460.32214
|
|
28584
|
Untitled by @meepodeep | Stardance
|
meepodeep
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @meepodeep | Stardance
|
1791826460.133548
|
1792690460.133548
|
|
9764
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826459.9422119
|
1792690459.9422119
|
|
21057
|
My very own WebOS by @hiwot | Stardance
|
hiwot
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: My very own WebOS by @hiwot | Stardance
|
1791826459.7297244
|
1792690459.7297244
|
|
12853
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826459.5726442
|
1792690459.5726442
|
|
33220
|
Untitled by @Hima_Shreyas_Nagumalla | Stardance
|
Hima_Shreyas_Nagumalla
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Untitled by @Hima_Shreyas_Nagumalla | Stard Title: Untitled by @Hima_Shreyas_Nagumalla | Stardance...
|
1791826459.3829
|
1792690459.3829
|
|
51993
|
Formula Apex by @adityajain1225 | Stardance
|
adityajain1225
|
0
|
0.28
|
0
|
[]
|
[{"post_id": 51138, "ts": "202 [{"post_id": 51138, "ts": "2026-08-20T17:10:47Z", "hours": 0.2797, "text": "Stated the Project completed the configs"}]...
|
Title: Formula Apex by @adityajain1225 | Stardance Title: Formula Apex by @adityajain1225 | Stardance
Devlogs:
Stated the Project completed the configs...
|
1791826459.1616056
|
1792690459.1616056
|
|
51990
|
Dead Man's Hand by @daval | Stardance
|
daval
|
0
|
0.43
|
0
|
[]
|
[{"post_id": 52493, "ts": "202 [{"post_id": 52493, "ts": "2026-08-22T17:07:58Z", "hours": 0.4333, "text": "🛠️ August 22th, 2026 - Tenth Build Session: External Fillets & More Simulations This build session focused on strengthening the outside of the air frame, specifically next to the fins, by using a “fondant tool”—a rounded tool that creates smooth finishes—and epoxy resin, a connection between the lower body tube and the fins can be created, although aerodynamically it doesn’t do much besides reducing interruption of laminar flow, it’s aesthetically pleasing and very recommended by my tutor. Besides that, I also made more simulations on OpenRocket, simulating distinct wind speeds ranging from 9.4 to 10.4 mph—the average windspeed in Michigan according to USA Symbol. Plus another wind speed higher than usual, of 15 mph. My mentor also recommended I slightly changed my design, I was planning on optimizing time by only doing the switchband and the nose cone red, and making everything else black, since it would be faster, but my mentor told me that although painting the fins red would be more time consuming, it would be worth it, so I took his advice. The launch date is marked as September 26th 2026."}]...
|
Title: Dead Man's Hand by @daval | Stardance
Title: Dead Man's Hand by @daval | Stardance
Devlogs:
🛠️ August 22th, 2026 - Tenth Build Session: External Fillets & More Simulations This build session focused on strengthening the outside of the air frame, specifically next to the fins, by using a “fondant tool”—a rounded tool that creates smooth finishes—and epoxy resin, a connection between the lower body tube and the fins can be created, although aerodynamically it doesn’t do much besides reducing interruption of laminar flow, it’s aesthetically pleasing and very recommended by my tutor. Besides that, I also made more simulations on OpenRocket, simulating distinct wind speeds ranging from 9.4 to 10.4 mph—the average windspeed in Michigan according to USA Symbol. Plus another wind speed higher than usual, of 15 mph. My mentor also recommended I slightly changed my design, I was planning on optimizing time by only doing the switchband and the nose cone red, and making everything else black, since it would be faster, but my mentor told me that although painting the fins red would be more time consuming, it would be worth it, so I took his advice. The launch date is marked as September 26th 2026....
|
1791826458.9834743
|
1792690458.9834743
|
|
14825
|
Comic AI by @coopradloff | Stardance
|
coopradloff
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: Comic AI by @coopradloff | Stardance
|
1791826458.790522
|
1792690458.790522
|
|
45026
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826458.628532
|
1792690458.628532
|
|
45023
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826458.4283574
|
1792690458.4283574
|
|
45020
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826458.2301817
|
1792690458.2301817
|
|
45009
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826458.0407033
|
1792690458.0407033
|
|
45008
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826457.8520288
|
1792690457.8520288
|
|
28462
|
Moth ( Finance tracker ) by @Henrique18 | Stardanc Moth ( Finance tracker ) by @Henrique18 | Stardance...
|
Henrique18
|
0
|
8.68
|
0
|
[]
|
[{"post_id": 37383, "ts": "202 [{"post_id": 37383, "ts": "2026-07-30T02:05:59Z", "hours": 2.4183, "text": "Implementation of cursor movement and interface changes I implemented the cursor movement logic to enable future record viewing. Additionally, I modified the menu and added some new keybindings."}, {"post_id": 35540, "ts": "2026-07-27T01:31:48Z", "hours": 3.91, "text": "Continue implementing ncurses in the project. This time, implement the rendering of Unicode icons—such as bars—to improve the program’s interface."}, {"post_id": 22556, "ts": "2026-07-05T02:27:03Z", "hours": 1.4708, "text": "I started implementing the ncurses library in the project. I created the logic to make the UI responsive and improved the input handling."}, {"post_id": 21556, "ts": "2026-07-03T16:04:06Z", "hours": 0.8831, "text": "I improved the way the bars separating the UI are printed."}]...
|
Title: Moth ( Finance tracker ) by @Henrique18 | S Title: Moth ( Finance tracker ) by @Henrique18 | Stardance
Devlogs:
I improved the way the bars separating the UI are printed.
I started implementing the ncurses library in the project. I created the logic to make the UI responsive and improved the input handling.
Continue implementing ncurses in the project. This time, implement the rendering of Unicode icons—such as bars—to improve the program’s interface.
Implementation of cursor movement and interface changes I implemented the cursor movement logic to enable future record viewing. Additionally, I modified the menu and added some new keybindings....
|
1791826457.6458972
|
1792690457.6458972
|
|
34725
|
LogOS by @Zaloguj12 | Stardance
|
Zaloguj12
|
0
|
0.0
|
0
|
[]
|
[]
|
Title: LogOS by @Zaloguj12 | Stardance
|
1791826457.4654262
|
1792690457.4654262
|
|
2054
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826457.2749183
|
1792690457.2749183
|
|
8572
|
NULL
|
NULL
|
0
|
0.0
|
0
|
[]
|
[]
|
|
1791826457.08985
|
1792690457.08985
|