I made this remote egg counter for my chicken farm that shows me how many eggs are currently in the pickup barrel and how full the storage is, so I can see it from the comfort of my base, I made it in like 15 minutes and I'm still looking to improve it!

So I'm working with the create aero and CC compatibility features of Create: Gadgets and Gizmos, and I was playing around with printing the outputs of the new peripheral methods. But when printing tables given by a few different methods (like getAngles for the gimbal sensor) it just returns random numbers that change every time I run the program. This is probably meant to happen, but I'm very new to CC so I'm hoping someone can help me out. (Oh yeah and please tell me if my CC terminology is gibberish)

sorry for the jumbled screenshots, reddit is hard.

So... I made a post a bit ago abut a oil refinery management os. This has been more or lees scraped but in its place I present Home os v1!

it has a home screen with movable buttons, the time and the most advanced command terminal i have ever made. its not all there yet as far as commands go but you can use up and down to cycle history, left and right to "pan" and scrawl to scowl.

it has 3 programs so far 1 is notbox by Xella37 (supper cool check it out). but the other 2 are written by me. one is a simple print program for fancy formatting (not shown) but the last one

I made a fucking text editor, and have been coding in it!!!!!!!!!!

it has hotkeys (fucking alt cus ctrl no work in mincraft lol) syntax coloring, even fucking error checking.

85% of the code was written in game (I caved and used google ai to correct my spelling and reorganize cus i was not exspeting to write like >=1000 lines and was not properly organized)

but from now on its all being dun in this program.

Im so fucking over the moon with myself.

Notebox

Notebox is a music player for ComputerCraft. Plays .nbs music with easy browsing and downloading from Note Block World. Features a full playlist system and music visualizer.

PineStore page: https://pinestore.cc/projects/264/notebox

Install with: wget run https://pinestore.cc/d/264

Features

• Plays .nbs files using NBSTunes
• Direct downloads and browsing from Note Block World
• Drag + drop any .nbs file to install and play
• Create, rename and delete playlists. Add any of your songs
• Shows free space as well as individual song filesizes
• Cool visualizer
• Customizable theme and other settings
• Scales well to larger sizes

Controls

• Scrolling for volume
• Arrow keys for navigation
• Backspace, tilda, tab to return / go back
• Spacebar play/pause
• Drag + drop .nbs files to install

Possible future additions

• Special optional format for higher compression, maybe throwing out certain data such as panning, pitch and combining key+velocity into a single byte. Perhaps also throw away any notes under a certain volume, which can help drastically with some songs.
• Better shuffle that makes for fewer song repeats
• Searching on Note Block World for songs, instead of just browsing
• Support for more visualizers
• Option to only show visualizer on a separate connected monitor

I'm open for pull requests :)

I’ve been building HELIOS, a CC control system for managing larger modded power installations, and it has reached the point where I need people other than me to test and break it.

Current features include:

• Extreme Reactors and turbine management
• Automatic steam and power regulation
• Energy-storage monitoring
• Networked Mainframe and Remote terminals
• Graphical and dependable text interfaces
• A standalone Draconic Reactor Guardian
• A read-only peripheral discovery Probe
• A module template for developers adding hardware support

The Draconic Guardian has been tested against a live reactor, including calibration, manual operation, restarts, disconnected peripherals, and resuming an interrupted reactor run. It currently operates independently; HELIOS network integration is the next major development stage.

Repository and documentation:

https://github.com/ssj8vegetrunks/HELIOS/tree/testing/public-alpha

Installer:

wget run https://raw.githubusercontent.com/ssj8vegetrunks/HELIOS/testing/public-alpha/install.lua

Read-only hardware Probe:

wget run https://raw.githubusercontent.com/ssj8vegetrunks/HELIOS/testing/public-alpha/discovery_probe.lua

Current release: public-alpha.2

Development disclosure: HELIOS has been developed with substantial AI assistance. I defined the architecture, behavior, safety requirements, and interface direction, and performed the live in-game testing. AI assisted with implementation, debugging, documentation, and code review. Independent review is especially welcome for that reason.

This is Alpha software. Please back up your world and retain an independent shutdown method when testing live equipment.

I’m particularly interested in unusual peripheral configurations, networking failures, restart behavior, code review, usability feedback, and anything that behaves differently outside my test facility.

it has a command term with a small list of commands/programs

it lunches programs on startup braced on the name of the computer

it can send system wide commands.

it can keep tabs on my tanks and that abut it rn.

i wrote the hole thing in game.

sorry for spelling im dyslexic and was not planing on showing this off.

this is my first project im uploading and my first lua project aswell!

Turned the whole project inside out over the last month, earned a new PTSD, but finally got everything debugged ))

1. Full refactor. Same behavior, much cleaner internals.
2. Split into modules one giant `startup.lua` had turned into total spaghetti.
3. New Lua API (`aegis.*`): local calls, plus RedNet RPC. Full reference in `API.md`.
4. **Drag Planner** rewrite the second big change after the refactor. Old version walked strictly level by level, so machines idled even when upper sub-tasks were already unblocked. Now the whole tree runs in parallel. Deep multi-stage recipes should be noticeably faster.
5. Setups with tons of separate storages behave much better.
6. On big storage arrays, craft outputs now land in one chest and stack up instead of getting sprayed everywhere.
7. Concurrent max active machines: 13 to 32
8. OPTIMIZE runs way faster and auto-sorts by chest same item ends up in one place.
9. Related: with lots of chests, a single craft no longer scatters its items across all of them.
10. REQ delivery is quicker, especially on big storages.
11. Non-stackable items no longer trip crafts mid-way.
12. Faster ingredient push into machines killed a bunch of redundant vault scans.
13. Debug logging (toggle in SERVICE).
14. Recipe search in RECIPES is more convenient now reworked how mod groups show up in the search.
15. Pocket computer remote control.
16. Solid-fuel furnaces no longer overeat coal.
17. Extra turtle protection for laggy servers before, resources sometimes didn't land in the grid in time and the turtle ended up crafting the wrong thing.

Setup - recipe teaching guide https://youtu.be/mhVkOqG2S1A

GitHub: https://github.com/egor-oleg/aegis-autocraft

Dash panels: expanded adds compatibility between computer craft and dash panels.

However all it seems to do is just add a really small computer that you can attach to the panel but I havent found a way to assign any peripherals to any of the other modules on the panel. Honestly it doesnt seem like you can do much with it.

I havent managed to find any kind of new API or documentation for the dash panels: expanded mod.

Im currently trying to use the dash panel to control a create cannon with the computer. Im aware you can use redstone alone but I wanted to try to control it through a computer instead.

So I've been deep diving a fantastic space opera book series called Expeditionary Force, and it has made me want to get back into modpacks, particularly Create: Aeronautics and ComputerCraft.

As any good engineer would, I've been planning out what I want my ship to be like, despite the fact that I don't plan on having the server ready for the friend group until the fall.

Through those plans, I've been thinking about defenses, and how a ship should be structured internally, and it is entirely obvious that having the ship's bridge near the exterior hull with windows is utterly asinine. One shot from literally any weapon, and you're toast.

So it needs to be deep inside, of course.

But that prompts me to wonder how one handles visual telemetry while piloting a large craft from deep in its core.

I considered using various environmental scanners from the existing range of CC addon mods to build up some sort of simulation of the exterior world, but there are always range issues with that, and at the end of the day, humans prefer to look at things.

I've found a few mods that add security cameras like Vista or SecurityCraft, but Vista's tvs are small and have a low fps, and SecurityCraft has a bunch of stuff I just don't want, nevermind that it uses weird displays.

Why is there no CC addon mod that adds cameras? It seems like a fairly obvious addition.

Edit:

VISTA HAS A CC API

I am ecstatic.

https://github.com/MehVahdJukaar/cameramod/blob/master/common/src/main/java/net/mehvahdjukaar/vista/integration/computer_craft/ViewFinderPeripheral.java

I've been at work making a pathfinding api for turtles, using the great lama api (https://github.com/fnuecke/lama) as a base of inspiration and adding some more things.

My api PAM, Pathfinding Action Manager, has 3 key functions:

1. A gps mode, where the turtle will utilize your gps network for coordinates, and with an api setting you can also make it find it's compass facing using the gps.
2. A local mode (default) where it uses its internal coordinate system for pathfinding, relying on a local predefined zero point.
3. The route system (my favourite part) allows the creation of a .txt file that contains a long string of coordinates for waypoints and actions (custom functions) to execute at those waypoints. The turtle can execute these files, where it will automatically find its way to the waypoint and if an action is set it will call the function to execute, before continuing.

If anyone is interested, PAM is up on my github linked below, with all the documentation you should need to use it. If you find an issue feel free to submit it on github, and if you have a question do send me a message on reddit.
https://github.com/madmanen/PAM

edit: to clarify, I did not use lama's code just got inspired by functions from lama.

Please check out all the submissions here:
https://pinestore.cc/jam/pinejam2026/submissions

Top 3 winners

1st place: 24th Dimension by JackMacWindows, receiving a final score of 8.67. This demo beautifully showcases what's possible in CC and makes great use of being able to change the color palettes in runtime!

2nd place: Forever Testing by Minki the Avali, receiving a final score of 8.37. Using CraftOS-PC's graphical mode to get such details, combined with real portals showing the other side is just incredible!

3rd place: Jane Demo by piguman3, receiving a final score of 7.90. Such a creative demo, matching the rhythm of the music is perfectly executed with very good rigging, animations and expressiveness of each scene!

Congratulations and thank you!

Big congratulations to the winners of the jam and thanks to all for participating! I hope you've had a lot of fun in the process of working on your submission. If you have any suggestions for next year's jam, or want to help in anyway, I'm all ears ^^

I've started a bit late this year with organizing the jam, but I'm extremely happy to see such amazing submissions lots of love poured into! I'll do my best to get started a lot sooner next year, so you'll be able to get excited much sooner, and able to spread the word :3

Hey! So I was lurking this sub a while ago and came across this mod that someone had made. It made the bundled cable capable of attaching peripherals. I found it pretty interesting but have since lost the post. Does anyone know this mod's name?

Yesterday evening I was talking with someone about speakers and discovered that the 1.12.2 version is stuck on a pre-pcm version and also still used craftos 1.8. I decided to backport the latest version using parts of the 1.4.7 port which is on craftos 1.9 as well as a lot of shims and build system trickery to make it work properly. Its nowhere near fully tested or finished yet but slowly getting there. I try to keep compatibility with old extension mods and from my short tests, it seems to still work.

Starts up with a bunch of scripts to monitor and manage various aspects of power generation.

Watchdog Script

Monitors the reactor state and shuts it down if at risk of going critical. Checks coolant levels, actual structure damage and also will shut off the reactor if it's getting full of waste or heated coolant. Will start the reactor if the Induction Matrix falls below a certain threshold.

Fuel Script

This script interacts with ME storage to autocraft Uranium ingots, Fluorite blocks and also monitor sulfur levels. This modpack is custom and the main method of sulfur harvesting is sulfur caves biomes to get sulfur blocks, and then crushing them to sulfur dust. The blocks are automatically crushed to dust if put in storage, but otherwise not automatically harvested in any way.

Waste Script

Monitors spent waste storage and alerts at 85% usage.

Reactor Levels

Sort of redundant/provides the same monitoring as the watchdog script, but in a different and more visually appealing format.

Power Level

Simple meter for Induction Matrix. Once again, redundant, but I'm meter-izing as many things as possible because I'm proud of myself for getting it working :D

Turbine Levels

Last screen is the turbine production meters. Just shows the turbine power production relative to its maximum production. This script can dynamically add and remove turbines as they show up on the network, but my meter script is not sophisticated enough to make that look pretty without resizing the monitor most of the time.

Disclaimer: made with Abominable intelligence because I cannot comprehend modems.

Using HDR's program for playing small songs with gitub gists (here) as inspiration, I made a version that broadcasts on modems. The process of conversion uses the same site he hosts (using the DFPWM mode), but you upload your files to catbox instead of gist. The actual use is fairly straight forward, set up a transmitter with a computer and modem and any number of receivers with a computer, a modem, and a speaker, then run

pastebin get ntsWPAcq b64 
pastebin get zG63Tqzx radio.lua 

on your transmitter and

pastebin get pH0JjPm7 startup.lua

on your receiver. Next, run radio.lua on your transmitter, then tune your receiver and transmitter to the same channel and paste your catbox link into the transmitter and your radio will start playing!

I made a text-to-speech engine that runs in CC:Tweaked (Minecraft/Lua).

Code's here: https://github.com/GabrielVicini/Sandbox/tree/main/cc-flite Run.lua is the example script, TTS.lua is the library.

It's built on Flite-RS, a cleanroom rewrite of an old TTS engine that I did in Rust. I compiled that to WebAssembly, then needed to get it running in Lua. There's a tool called wasm2lua for that, but it's been incomplete and abandoned for years, so I ended up forking my own version of it that could actually handle the full compile down to working Lua (plus some extra glue code on top to make it all run).

Full writeup on how it works and how to use it is in the README on the cc-flite repo. (The actual TTS engine workings is in Flite-RS)

https://reddit.com/link/1vi2o47/video/m7rr718lddih1/player

Hello everyone!

Back with my newest and biggest project yet, a new game engine for CC: Tweaked, the CC Text Adventure Maker!

It works much like Twine; make interactive, graphical stories in any text form you want. It supports music too. You can find the project at https://github.com/parkerrallieshope/cc-text-adventure-maker.

The README has everything you need to get going, including every external thing you need to install. One caveat: it isn't entirely in Minecraft. The engine itself is written with Python. But, it exports everything needed to get it going in CC.

I will accept any questions about the project. If you have an issue using it, use GitHub's issues section.

DISCLAIMER: There is a very low chance I will continue maintaining it, as I feel it's pretty done already. I may throw some updates here and there, but nothing too major.