ROM ROMVoid95

ReadOnly Development Individual Contributor License Agreement

Thank you for your interest in contributing to open source software projects (“Projects”) made available by ReadOnly Development ("RoD"). This Individual Contributor License Agreement (“Agreement”) sets out the terms governing any source code, object code, bug fixes, configuration changes, tools, specifications, documentation, data, materials, feedback, information or other works of authorship that you submit or have submitted, in any form and in any manner, to RoD in respect of any of the Projects (collectively “Contributions”). If you have any questions respecting this Agreement, please contact [email protected]

You agree that the following terms apply to all of your past, present and future Contributions. Except for the licenses granted in this Agreement, you retain all of your right, title and interest in and to your Contributions.

Representations: You represent that, other than the Third Party Content and Third Party R

People assume that giving the game more leeway in terms of memory (RAM) usage makes it run better. This is actually not true, especially the common conception that “more ram = better fps”. So let me give you a somewhat technical explanation of why this is the case. I’m no expert in the matter either, but I believe I know enough to pass the knowledge around, so feel free to correct me if I mess something up.

Ok, so let’s start by talking about the Java Virtual Machine, and the concept of instance. The Java Virtual Machine, as you might know is what’s responsible for running java applications, which obviously includes minecraft, when you load it up, it needs to know how much memory it can work with, this is what you change when you allocate more memory to the game, how much space it has to fill with anything the application needs to use. Next off is an instance, in object-oriented programming, which Java falls under, an instance is, on very simple terms, an object, something that exists and has values. For exa

	<blockstate> == {
	"forge_marker": 1,
	"defaults": <variant>, // optional, added to all variants
	"variants": {
	"<property>": {
	"<value>": <variant> // variant definition for the specified value of this property; variants for multiple values can be specified.
	},
	"<variant name>": <variant>, // variant definition for the full variant string
	"<variant name>": [<variant1>, ...], // array of definitions for the full variant - result will be the random variant
	}

	task copyMiccore(type: Copy) {
	from '/submodule/MicdoodleCore/src/main'
	into 'src/main'
	}

	task subModule(type:Exec) {
	commandLine 'git', 'submodule', 'add', '-b', '1.12' 'https://github.com/micdoodle8/MicdoodleCore', 'submodule/MicdoodleCore'
	}

	===========================================================
	GalactiCraft Conquest 1.5.0 --> GalactiCraft Conquest 2.0.0
	===========================================================

	Added:
	- FTB Backups
	- GunpowderLib
	- JourneyMap Defaults
	- Pack Crash Info
	- SteveKunG's Lib

	package net.minecraft.client.gui.inventory;

	import com.google.common.collect.Lists;
	import java.io.IOException;
	import java.util.List;
	import java.util.Locale;
	import java.util.Map;
	import javax.annotation.Nullable;
	import net.minecraft.client.Minecraft;
	import net.minecraft.client.entity.EntityPlayerSP;

	I see this a lot. People assume that giving the game more leeway in terms of memory (RAM) usage makes it run better. This is
	actually not true, especially the common conception that “more ram = better fps”. So let me give you a somewhat technical
	explanation of why this is the case. I’m no expert in the matter either, but I believe I know enough to pass the knowledge around,
	so feel free to correct me if I mess something up.

	Ok, so let’s start by talking about the Java Virtual Machine, and the concept of instance. The Java Virtual Machine, as you might
	know is what’s responsible for running java applications, which obviously includes minecraft, when you load it up, it needs to know
	how much memory it can work with, this is what you change when you allocate more memory to the game, how much space it has to fill
	with anything the application needs to use. Next off is an instance, in object-oriented programming, which Java falls under, an
	instance is, on very simple terms, an object, something that exists and h