CC-Tweaked/gradle.properties

org.gradle.jvmargs=-Xmx3G

# Mod properties
mod_version=1.100.0

# Minecraft properties (update mods.toml when changing)
mc_version=1.17.1
mapping_version=2021.09.05
forge_version=37.0.85
# NO SERIOUSLY, UPDATE mods.toml WHEN CHANGING
Increase memory limit of the gradle daemon This has been standard in the mdk for a while, but never actually had to do this before. IntelliJ finally started hitting this limit when decompiling. 2021-09-18 11:42:36 +00:00			`org.gradle.jvmargs=-Xmx3G`

Several recipe improvements - Some performance improvements to JEI recipe resolver - Use a shared map for upgrade items, meaning we only need one map lookup. - Cache the basic upgrade recipes. - Use the MC version within project rather than version name. 2019-03-19 11:47:12 +00:00			`# Mod properties`
Bump CC:T version to 1.100 We're still a few days away from release, but don't think anything else is going to change. And I /really/ don't want to have to write this changelog (and then merge into later versions) on the 25th. 2021-12-21 14:55:01 +00:00			`mod_version=1.100.0`
Several recipe improvements - Some performance improvements to JEI recipe resolver - Use a shared map for upgrade items, meaning we only need one map lookup. - Cache the basic upgrade recipes. - Use the MC version within project rather than version name. 2019-03-19 11:47:12 +00:00
Bump versions 2019-11-23 09:58:54 +00:00			`# Minecraft properties (update mods.toml when changing)`
Update to Minecraft 1.17.1 - Remap everything to use MojMap class names too. This is what Forge uses, so \o/. This does NOT currently rename any classes to use suffix notation or BlockEntity. That will come in a later change. We do however rename references of "World" to "Level". - Move the test mod into a separate "cctest" source set. As Forge now works using Jigsaw we cannot have multiple mods defining the same package, which causes problems with our JUnit test classes. - Remove our custom test framework and replace it with vanilla's (this is no longer stripped from the jar). RIP kotlin coroutines. It's still worth using Kotlin here though, just for extension methods. - Other 1.17-related changes: - Use separate tile/block entity tick methods for server and client side, often avoiding ticking at all on the client. - Switch much of the monitor rendering code to use vanilla's built-in shader system. It's still an incredibly ugly hack, so not really expecting this to work with any rendering mods, but we'll cross that bridge when we come to it. 2021-08-03 20:46:53 +00:00			`mc_version=1.17.1`
Bump Forge version - Clean up NBT constants, replace with built-in ones - Switch over to the new capability system 2021-10-06 17:28:28 +00:00			`mapping_version=2021.09.05`
Some post-1.17 cleanup - Fix broken Javadoc references - Apply a couple of refactoring suggestions from IDEA 2021-10-13 16:46:29 +00:00			`forge_version=37.0.85`
Bump to 1.16.5 I don't think anyone still uses 1.16.4, so no point worrying about it. Closes #808 2021-06-05 11:32:27 +00:00			`# NO SERIOUSLY, UPDATE mods.toml WHEN CHANGING`