Rivoreo Source Code Repositories
src.rivoreo.one / minecraft / opencomputers / 12082391bb73900395976cec1393ee2c0a5fb1b7
commit12082391bb73900395976cec1393ee2c0a5fb1b7[log] [download]
authorFlorian Nücke <florian@nuecke.de>Fri Aug 15 01:29:23 2014 +0200
committerFlorian Nücke <florian@nuecke.de>Fri Aug 15 01:29:23 2014 +0200
tree466d3de25e26112ea9b1a1d06225cf7a33791b60
parent5ba5b3cea896a5ef90da91837c6f877b1476771c [diff]
Made hologram max scale setting use doubles instead of ints for more flexibility and reworded the comment in the config a little.
2 files changed
tree: 466d3de25e26112ea9b1a1d06225cf7a33791b60
  1. .gitignore
  2. LICENSE
  3. LICENSE-jnlua
  4. LICENSE-luaj
  5. LICENSE-mods
  6. LICENSE-typesafe
  7. LICENSE-unifont
  8. README.md
  9. assets/
  10. build.gradle
  11. build.properties
  12. gradle/
  13. gradlew
  14. gradlew.bat
  15. libs/
  16. settings.gradle
  17. src/
README.md

Welcome to OpenComputers

OpenComputers is a Minecraft mod that adds programmable computers and robots to the game. The built-in computer implementation uses Lua 5.2 and is fully persistent. This means programs will continue running across reloads. For more information, please see the wiki. Feel invited to visit the community forums or drop by in the IRC channel #oc on esper.net.

A few useful links:

###Experimental Builds You can find experimental builds on the build server. Expect these to be generally more unstable than builds marked as releases. Use these at your own risk, but - when using the latest one - please do report bugs you encounter using them. Thanks!

License / Use in Modpacks

This mod is licensed under the MIT license. All assets are public domain, unless otherwise stated; all are free to be distributed as long as the license / source credits are kept. This means you can use this mod in any mod pack as you please. I'd be happy to hear about you using it, though, just out of curiosity.

Contributing

###Assets and Localizations

  1. Translations
    Translations to other languages are very much appreciated. You can find the localization files in this folder. If a localization you wanted to create already exists, please take the time to see if the present one is complete - the strings change every so often, invalidating some of the translations. If you start a fresh localization, please base it off of the English or German one, those are the ‘master’ localization files. If you add a new language, please also add it to the pack.mcmeta file. Keep it sorted alphabetically, use the name and region Minecraft itself uses. If you don‘t know how to do that, that’s OK, I'll do it later.
  2. Textures
    If you would like to contribute better textures for certain items or blocks, feel free to pull-request them. If you would like to contribute alternative textures, make it a resource pack, and post it on the forums, for example.
  3. Documentation
    Help with keeping the wiki up to date would be really appreciated. If you notice anything amiss and know better, fix it. If you don't ask someone who does, then fix it. If you had a question answered, consider adding that information somewhere in the wiki where you would have expected to find that information.
    There are also the files containing the ingame help, which could probably be much better than they are right now. Improvements to them, and new ones (e.g. for the libraries, such as text or sides) would help a lot. Thanks!
  4. Robot Names
    Robots get a random name when placed (unless set with an Anvil). The list the names are chose from can be found here. Feel free to pull request additional names! I added the names of a few contributors so far - if your name is in the list and you don‘t want that, please let me know, or just pull-request the name’s removal. Sorry in that case! If you contribute to the project and would like your name in the list, please feel free to add yourself to the list in a pull-request.

###Bug fixes, features and scripts

  1. Bugs
    If you‘ve found a bug, please report it in the issue tracker, after checking it has not been reported before - and possibly even fixed by now. If you think you can and have fixed it, feel free to do a pull request, I’ll happily pull it if it looks all right to me - otherwise I'll gladly tell you what to change to get it merged.
  2. Features
    If you‘d like to propose a new feature, take it to the forums or the issue tracker. If you’d like to contribute code that adds new features, please make sure to discuss the feature with me, first - again, the issue tracker is an OK place for this, there are a couple of feature requests there, already. Alternatively start a topic on the forums to discuss the feature, and / or stop by the IRC to talk about it. Blind / unexpected feature pull requests might very well not make it, so save yourself some time by talking about it, first! Thanks.
  3. Scripts / Programs
    OpenComputers generates floppy disks in dungeon chests that can contain data from a selection of ‘loot’ directories. For example, the IRC client and the Better Shell (besh) are two programs that can be found on such loot disks. If you'd like to contribute a program that can be found this way, please have a look at the loot readme, which explains how to add custom loot. Simply pull request your loot!
  4. Core Scripts
    If you would like to contribute scripts to the “core” Lua code (which basically defines ‘OpenOS’), please have a look at the code conventions for Lua to save us all some time. Bug fixes are always welcome. Additional programs and features should be kept small. Bigger programs (rule of thumb: larger than 3KiB) should go onto loot disks.

Extending

In your own mod

To use the API in your own mod, either get the API JAR from the build server, or if you're using gradle, add a dependency to the maven repo:

repositories {
    maven { url = "http://maven.cil.li/" }
}
dependencies {
    compile group: 'li.cil.oc', name: 'OpenComputers', version: 'MC1.6.4-1.2.3.280', classifier: 'api'
}

Adjust the version number accordingly to the version you'd like to build against.

To run the mod in your development environment, download the deobf JAR from the build server and drop it into your dev env's eclipse/mods folder. Important: mark the api/java/codechicken/lib/vec folder as excluded in your IDE, to avoid issues when running/building the project in it.

Alternatively, leave out the api classifier and you can build against the deobf JAR directly. This way you don't have to add it to your mods folder, but you will have to add -Dfml.coreMods.load=li.cil.oc.common.launch.TransformerLoader to the VM options in your run configuration.

If you have any questions, please do not hesitate to ask, either in the forums or in the IRC!

OpenComputers

Want to tinker with the mod itself? Here is how - for IntelliJ IDEA users. For eclipse I assume the process will be similar.

Important

  • Make sure you have the Gradle plugin enabled in IDEA (File->Settings->Plugins).
  • Make sure you have the Scala plugin enabled.

Clone the repository, then in it run
gradlew setupDecompWorkspace
to setup the workspace, including assets and such, then
gradlew idea
to create an IntellJ IDEA project.

Open the project and you will be asked to import the Gradle project (check your Event Log if you missed the pop-up). Do so. This will configure additionally referenced libraries - at this point CodeChickenLib and ForgeMultipart. Since CCL will download stuff again and you'll get conflicts otherwise, go into the project settings and mark CCL and FMP as “provided” (instead of the default, “compile”).