The source code to my tech mod RotaryCraft.
Java
Switch branches/tags
Nothing to show
Clone or download
Latest commit 1a0bb1d Jul 2, 2018
Permalink
Failed to load latest commit information.
API Update 883 Jun 1, 2018
Auxiliary Update 884 Jul 3, 2018
Base Update 884 Jul 3, 2018
Blocks Update 876 Nov 5, 2017
Containers Update 882 Apr 17, 2018
Entities Update 875 Nov 2, 2017
GUIs Update 883 Jun 1, 2018
Items Update 883 Jun 1, 2018
ModInterface Update 884 Jul 3, 2018
Models Update 878 - v19a Nov 10, 2017
Registry Update 884 Jul 3, 2018
Renders Update 883 Jun 1, 2018
Resources Update 882 Apr 17, 2018
Sounds Update 871 Aug 19, 2017
Textures Update 884 Jul 3, 2018
TileEntities Update 884 Jul 3, 2018
.gitattributes Creation on GitHub May 28, 2013
.gitignore Add XMLs Nov 28, 2013
ClientProxy.java Update 878 - v19a Nov 10, 2017
CommonProxy.java Update 870 - v18a Aug 8, 2017
ConnectedGlassRenderer.java Update 875 Nov 2, 2017
CubicalMachineRenderer.java Update 870 - v18a Aug 8, 2017
DecoTankItemRenderer.java Update 883 Jun 1, 2018
ExtraIronGenerator.java Update 870 - v18a Aug 8, 2017
GuiHandler.java Update 876 Nov 5, 2017
ItemMachineRenderer.java Update 870 - v18a Aug 8, 2017
License.txt Update 853 Feb 10, 2017
PacketHandlerCore.java Update 882 Apr 17, 2018
PipeBodyRenderer.java Update 883 Jun 1, 2018
README.md Update README.md Apr 26, 2017
RotaryChests.java Update 870 - v18a Aug 8, 2017
RotaryConfig.java Update 883 Jun 1, 2018
RotaryCraft.java Update 882 Apr 17, 2018
RotaryEventManager.java Update 875 Nov 2, 2017
RotaryNames.java Update 884 Jul 3, 2018
RotaryRecipes.java Update 884 Jul 3, 2018
RotaryRegistration.java Update 873 Sep 30, 2017
logo.png Update Sep 22, 2014
logo2.png Update Sep 22, 2014

README.md

RotaryCraft

The source code to my tech mod RotaryCraft.

@author Reika

Copyright 2013-2017

All rights reserved. Distribution of the software in any form is only allowed with explicit, prior permission from the owner. See License.txt and the official licensing page for more details.

Pull Requests

If you wish to suggest code, I actually do not merge pull requests, for three reasons:

One, I have had very bad experiences with errors on GitHub's part when accepting pull requests. The first and last time I did so, because of the timing of the PR relative to other commits (I noticed the PR about two weeks after it was submitted, and made commits, including to the changed files, in the interim), it corrupted the entire repository and the code on my machine, forcing me to roll back 3-6 months worth of commits. The only reason I did not lose that much code is because I had another copy on another computer, so I was able to roll it back (with the code safely backed up), then re-load the backup and make one commit with 3-6 months of changes. Because I do not regularly check GitHub, this situation would be very likely to repeat itself.

Two, the code is not written by me and thus I do not have a full understanding of how it works; even if I can trace the actual program logic, I know little of why it is designed the way it is - any programmer will agree that for any non-trivial algorithm, they understand their code better than anyone else - and much more importantly, nothing about how to change it if I need to fix or change it later, especially in the cases of Minecraft version updates. Use of supplied code has already introduced bugs and crashes for this exact reason.

Three, because of the complexity of much of RC code, I do not fully trust potential code submitters to understand all of the implications of their changes. Several times fixes for real issues have been suggested, including as PRs, that cause auxiliary problems, some cripplingly severe, because the author was not aware of the effects of their changes.

However, you can still suggest code, even in the form of a pull request if you like; I will simply add it manually. Because of the license on this repository, the rights to any code submitted - this would apply even to PRs - is released to me under an unrestricted license.