Important!
CCTweaks is a core mod and makes modifications to the internals of ComputerCraft. Whilst the mod is thoroughly tested there may be issues. If you encounter any bugs report them here and not on the ComputerCraft issue tracker. This will ensure a faster response time and will ensure you do not frustrate DanTwoHundred.
Thanks :)/>!
Minecraft 1.10.2/1.11.2?
Whilst there isn't a stable build of ComputerCraft for Minecraft 1.10.2 and 1.11.2, there is support for both on the repository. You can download builds of ComputerCraft for 1.10.2 and 1.11.2 from the unofficial CC build server.
Features
Spoiler
Programming (More up-to-date list here)- Custom computer timeout
- Whitelist debug API
- Fix the binary strings (for fs, http, rednet and os.queueEvent)
- TCP socket API (socket)
- Compression API (data)
- LuaJC compiler (compiles Lua code to Java for performance boost)
- Cobalt VM (reentrant fork of LuaJ)
- Custom termination handler
- Several bugs fixed (any object error messages, string pattern matching, number format strings)
- Return HTTP handle on failures
- Allow getting headers from HTTP responses
- API for adding custom APIs
- Custom ROM for computers
- Blacklist turtle verbs - no more turtle.inspect if you don't like it.
- Turtle refuel using RF/EU
- Turtle tool host - use any tool with turtles
- Turtles named dinnerbone or Grumm turn upside down [1.7.10 only]
- Networking API: add custom network components
- Multidimensional modems (connect wired networks together)
- Full block modems (connect to peripherals on 6 sides)
- Multipart support
- Item transport through OpenPeripheral [1.7.10 only]
- Beautiful network visualiser
- Computer upgrades - convert normal computers to advanced!
- Debug Wand - add the debug API to any computer
- Monitors emit light
- Pocket computer peripherals [1.7.10 uses Peripherals++, 1.8+ is built in]
Downloads
You can download from Curse.
The source is under the MIT license, and is on GitHub.
Bugs, issues, feature requests
Feedback is always welcome, however I would love it if this could go on the issues section of the GitHub repo instead. It just is easier for me to track progress on things.