Digiline channels meta bloat
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 23
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Most machines never get used with digilines, yet they get a channel assigned with their coordinates.
Does anyone ever use this predefined channel in their code?
Wouldn't it be less bloat if a non-unique and short channel was preset?
Like hb, mb, lb for HV, MV and LV battery boxes. Or just plain 'bb' for all tiers.
'ss' for switching stations, 'ff' force fields and so on.
"leave it empty (remove generator and just empty) and allow actually using empty channel just like many other digiline devices do."
Above done for battery boxes, do the same for rest:
- Battery box
- Switching station (formspec is good, remove channel generator)
- Power monitor (formspec is good, remove channel generator)
- Nuclear reactor core
- TBD: Remove "enable digiline" checkbox from formspec and keep digiline always enabled
- Tool workshop
- ?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the digiline channel generators and formspecs for the remaining Tool Workshop and nuclear reactor work, then compare them with the completed battery box, switching station, power monitor, and reactor changes. Done means the remaining channel generators are removed and the reactor's digiline-enable checkbox decision is implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- game-dev
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100