CCPE — CC Peripheral Extender

Wireless sensor access for ComputerCraft: Tweaked on NeoForge

What is this?

CCPE adds peripheral extender blocks to CC:Tweaked. Attach a sensor to any block, set a channel number, and wirelessly read that block's data from Lua — no cables, no distance limits.

local pe = require("ccpe.pe")
local data = pe.getAll(1)              -- read full NBT of block on channel 1
local cnt  = pe.get(1, "Items[0].Count")  -- read a specific field by path

Features

CC:Tweaked's standard peripherals require the computer to be directly adjacent to the target block. While many mods add peripheral adapters for their blocks, not every block has one.

CCPE's sensor caches block data via NBT snapshots — works with any block, no need to wait for mod authors to add peripheral support.

The cache refreshes every server tick (50ms), and Lua reads take ~0.02ms per call, suitable for high-frequency monitoring.

API

📡 Wireless Block Reading

• Attach sensor to any block
• Read NBT via pe.get(channel, path) or pe.getAll(channel)
• Path syntax: "Items[0].Count", "ForgeData.CustomName", etc.

🧭 Navigation Table Integration

• pe.getNavTargetPos(ch) → {x, y, z} — target world coordinates
• pe.getNavSelfPos(ch) → {x, y, z} — self world coordinates
• pe.getNavDistance(ch) → number — distance to target (meters)
• pe.getNavRelativeAngle(ch) → number — bearing angle (degrees, 0~360)

🚀 Physics Data (requires Sable/physical structure)

Velocity methods require sensor attached to simulated:velocity_sensor

Method	Return	Description
getPhysicsVelocity(ch)	{x, y, z}	Ground velocity (m/s)
getPhysicsAirVelocity(ch)	{x, y, z}	Airspeed, wind subtracted (m/s)
getPhysicsAngularVelocity(ch)	{x, y, z}	Angular velocity (rad/s)

📶 Wireless Redstone

• pe.setRedstoneOutput(ch, 0-15) — transmit redstone signal (mainThread=true)
• pe.getRedstoneOutput(ch) — read transmitted signal
• pe.getRedstoneInput(ch) — read received signal

🔌 Peripheral Proxy

• pe.getPeripheral(ch) — wirelessly access the attached block's CC:T peripheral methods

📻 Redstone Transceiver

• Channel-based Create Redstone Link integration
• receiver.setRedstoneSignal(channel, 0-15) — transmit to Create network (mainThread=true)
• receiver.getRedstoneSignal(channel) — read Create network signal

🏗️ Chunk & Physics Body Loading

The sensor can keep its target area loaded:

Physics body mode automatically tracks the structure's movement, relocating PORTAL tickets to the body's current chunk. Bearing connection chains are refreshed every 5 seconds.

Config (config/ccpe-common.toml):

• sensorChunkLoadEnabled — enable chunk loading
• sensorMaxForceLoad — max concurrent loaded sensors
• sensorPortalTicketRadius — PORTAL ticket radius

Quick Start

local pe = require("ccpe.pe")

-- Read a chest's inventory
local items = pe.getAll(1)
for k, v in pairs(items) do print(k, v) end

-- Navigation guidance (sensor on navigation table required)
local target = pe.getNavTargetPos(2)
local dist   = pe.getNavDistance(2)
local angle  = pe.getNavRelativeAngle(2)
print(string.format("Target: %.0fm away, bearing %.1f°", dist, angle))

-- Physics data
local mass = pe.getPhysicsMass(3)
local com  = pe.getPhysicsCenterOfMass(3)
print(string.format("Mass: %.1f kg, COM: %.1f, %.1f, %.1f", mass, com.x, com.y, com.z))

-- Wireless redstone
pe.setRedstoneOutput(4, 15)  -- activate sensor on channel 4

-- Create redstone link control
local redstone = peripheral.find("ccpe:redstone_transceiver")

redstone.setRedstoneSignal(5, 15)  -- transmit to Create network on channel 5
redstone.getRedstoneSignal(3)  -- read Create network signal on channel 3

Requirements

• NeoForge 1.21.1
• CC:Tweaked 1.118.0+
• Create 6.0.10+
• Simulated (Create: Aeronautics) 1.3.0+
• Sable 2.0.3+

Performance

Read operations ~0.02ms/call, redstone write operations ~50ms/call.

Where is Create Microcontrollers

why create microcontrollers 404