CobbleGen

—

—

## About

**CobbleGen** is an MC mod that allows you to customise/randomise cobblestone (basalt and stone) generator.

As of v5.0, CobbleGen is officially supported for both Fabric-like and Forge-like modloaders. Because of how the mod is designed, the mod should still work on future versions of Minecraft, just don’t expect integration (such as Create mod integration, REI/EMI/JEI integration) to work properly. Click here to see detailed version tracker.

The Fabric JAR should work on Quilt, the mod is designed to only rely on Vanilla code as much as possible.

The Forge JAR should also work on NeoForge (MC 1.20.1 only). Support for Forge will be stopped at MC 1.20.1, please consider migrating to NeoForge to use CobbleGen on Forge for MC 1.20.2 or newer!

### Features

– Supports Fabric/Quilt and NeoForge/Forge
– REI/EMI/JEI Integration
– Customisable cobblestone, stone, and basalt generator
– Randomised the generated block with a customisable weight value
– Customisable modifier to give your players more challenge
– Dimension whitelist/blacklist
– Y-level limiter
– Supports tag (put `#mod_id:tag_id` instead of putting `mod_id:block_id`)
– Supports Create mod
– Pipe/Pump support
– Porting Lib compatibility on Fabric/Quilt (Fixes Limestone and Scoria Generators)
– Advanced custom generator (custom fluid interaction)
– Fluid Interaction API for developers

More features are coming soon!

#### Planned Features
– Modifier(s) position (No longer limited to “below generated block”)
– Webapp for modpack developers to easily configure the generators
– Biome whitelist/blacklist

### Usage

This mod is mostly server-side, but it’s recommended to also have it installed in the client-side for REI/EMI/JEI support.

Out of the box the mod doesn’t do much, it will generate default config where cobblegen generates deepslate at deepslate level, random ores when there’s bedrock underneath generated block, etc. To use the mod to its full potential you need to configure it yourself.

## Configuration

If you’re not familiar with JSON you could try CobbleGen Configurator, but keep in mind that the website is still work-in-progress, so some features are still missing from the website.

The mod provide you with 3 layers of config: default, custom, and advanced.
– **Default**: The most basic modification, it lets you to replace vanilla generated block. E.g. tell the gen to generate Diamond Block instead of Cobblestone.
– **Custom**: Lets you to modify the generator’s modifier, similar to how you require to have Soul Soil to generate Basalt, but works with any type of generator. E.g. tell the gen to generate Ores when the block is generated above Bedrock.
– **Advanced**: Lets you to modify fluid interaction, you can use it to use modded fluid to generate a block. E.g. tell the gen to generate Diamond Block if Honey fluid touches Milk fluid.

The config file is located in `config/cobblegen.json5`, the format should be pretty straightforward:

## Compatibility
~~Any mods that modify fluid interaction behaviour potentially have a conflict with CobbleGen. With the exception of Porting Lib (the Create mod).~~

**Starting from v4.0**, CobbleGen has been rewritten to reduce mod incompatibility as much as possible.

CME is Bad

# Abstract
Players and modpack developers sometimes find the game crashed with `ConcurrentModificationExceptions` (CME) and `IndexOutOfBoundsExceptions` (IOOBE), which only give stacktrace of current thread and are hard to trace which mod causes them. Here’s one of the crashes which is caused by SimpleReloadInstance in 1.20.1 Forge:


So this is what the mod is developed for. Players who install this mod and add javaagent to JVM Argument correctly will receive a full log for modification history of a certain collection:


# Usage
First, add this jar to mods folder.

Second, edit your Java Virtual Machine Argument in your launcher. Add `-javaagent:mods/CMESuckMyDuck-.jar=;;;`.

Finally, run the game, play and wait until the crash happens.

# Usage for Other Java Projects
This mod can not only be used for Minecraft debugging, but also be utilized to debug other java projects. Similar to Minecraft. The only different step is that you should add gson and asm jar to classpath (`-cp`) before javaagent, and add our `CMESuckMyDuck-.jar` to classpath after javaagent.

# Arguments
##
A full name of the class, which has a container that you would like to monitor. Use “ instead of `.` (a.k.a. the internal name of class).

##
A field name of the container in target class, which you would like to monitor. For Forge, use SRG name. For Fabric, use intermediary name. For NeoForge, use official name.

##
Currently, we only support three containers: `List`, `Set`, `Map`. This argument indicates the type of monitored container.

## `static` or `nonstatic`. This argument indicates the container is a static field or non-static field.

# How to get and
Let’s start with an example.

First, take a look at the stacktrace of CME/IOOBE:


Second, read the source code of SoundEngine and confirm which container is facing this issue:


Now we know we should monitor map `field_217942_m` (`instanceToChannel` in `SoundEngine`). Keep going.

Third, install this mod, and add “`-javaagent:mods/CMESuckMyDuck-1.0.0.jar=net/minecraft/client/audio/SoundEngine;field_217942_m;Map;nonstatic`” to Java Virtual Machine Argument. Relaunch the game and wait for the next crash.

Finally, open `CMESuckMyDuck.log` file and you will see which thread and which mod has concurrently modified the container.

# Examples (JVM Arguments)
## ConcurrentModificationException from SoundEngine in Forge 1.16.5 Environment
`-javaagent:mods/CMESuckMyDuck-1.0.0.jar=net/minecraft/client/audio/SoundEngine;field_217942_m;Map;nonstatic`

## ConcurrentModificationException from PotionBrewing in Forge 1.20.1 Environment
`-javaagent:mods/CMESuckMyDuck-1.0.0.jar=net/minecraft/world/item/alchemy/PotionBrewing;f_43494_;List;static`

## ArrayIndexOutOfBoundsException from Zeta mod
`-javaagent:CMESuckMyDuck-1.0.0.jar=org/violetmoon/zetaimplforge/event/ForgeZetaEventBus;convertedHandlers;Map;nonstatic`

# Other options
## Log Level
Use system property `-Dcme_suck_my_duck.log_level=` to set custom log level.

Default 1, which means no debug message will be logged.

Users can set it to 0 to output debug message, which is not recommended – query functions like Map#get, Set#containsAll will also be logged when set to 0, and make the file very very long.

## ASM API Version (v1.0.2+)

In order to maintain compatibility with the latest version of Minecraft, this mod is compiled with asm version 9.7. For older versions of Minecraft (such as 1.12.2), API level operations such as ASM_9 cannot be applied, so players need to use `-Dcme_suck_my_duck.asm_api_version=` to modify the ASM API version compatibility. For example, game version 1.12.2: `-Dcme_suck_my_duck.asm_api_version=5`.

## File Max Entries (v1.0.3+)

Since we notice that when crash happens, the last few operations in the log are much more important than the previous ones. So our mod adopts a paging strategy after v1.0.3, and only the last two pages are retained at the end. The number of logs output on each page (that is, the number of operation call stacks) is fixed, and the default value is 500. Players can use `-Dcme_suck_my_duck.file_max_entries=` to modify the maximum number of elements on the page.

## Whitelist of Constructor (v1.0.3+)

Sometimes a container in a certain class is used in many places (eg. CompoundTag#tags). Directly using this mod will cause the log to be too long or the valid content to be replaced by subsequent operations. Therefore, players can specify an additional constructor whitelist to monitor the corresponding container in the corresponding class of a specific module. The default is empty, that is, there is no whitelist. Players can use `-Dcme_suck_my_duck.whitelist_constructor_stacktrace=` to specify it. If any line in the stack trace where the container is constructed includes the content of the whitelist string, the container will be monitored – otherwise, the container will not be monitored, which greatly simplifies the log output information.

## Transform to Thread Safe (v1.0.4+)
Use system property `-Dcme_suck_my_duck.transform_to_thread_safe=true` to transform the field into a thread-safe container.

This is NOT recommended unless you like slowness and don’t want to fix the problem.

## Inject method (v1.0.4+)
Use system property `-Dcme_suck_my_duck.inject_method=true` to switch to inject mode.

If set, you should use `-javaagent:CMESuckMyDuck-.jar=;` and whenever this method is called, you will receive a stack trace in log files.

## Ignore threads (v1.0.5+)
Use system property `-Dcme_suck_my_duck.ignore_threads=;;;…` to ignore some thread that is expected to modify the given container (or call the given method). For example, `-Dcme_suck_my_duck.ignore_threads=”Server thread”`.

## Stop logging early (v1.0.7+)
Use system property `-Dcme_suck_my_duck.stop_logging_if_exception_created=false` to stop logging if critical error occurs.

## Trace ID Updater (v1.0.8+)
Use system property `-Dcme_suck_my_duck.trace_id_updater=;` to update trace ID when calling the given method. This might be useful in inject mode.

## Monitoring Local Variables (v1.1.0+)
Use system property `-Dcme_suck_my_duck.local_var_index=` to monitor local variable at given index in the given method.

If set, you should use `-javaagent:CMESuckMyDuck-.jar=;;`. By the way, the index can be reused by different local variables. So you might have to use `-Dcme_suck_my_duck.match_local_index=` to specify the ordinal of ASTORE operation to indicate which local variable to monitor.

# Conclusion
I like eating peking duck. It’s so delicious!


Clear wither hearts

Makes** withered hearts clear** to see if they are there or not.

Clear Lag

This data pack uses methods from server software like Spigot and Paper to optimize performance.
You can configure many settings and even enable a small anti-crash for your server.

# How to use
Use `/function clearlag:menu` to modify settings, view clear statistics and configure which clear/warning messages are shown.
# Methods this data pack uses
– Shorter item/experience orb despawn time (valuable items and death items wont get removed through clears)
– Automatic clears which remove all items in a configurable interval
– Freezes unused entities
– Merges experience orbs
– Removes collision from farm animals

The data pack was created with the aim of being high-performing and efficient, and should not cause any lag on its own.

## Server software
Works on vanilla, bukkit, spigot, paper, all forks of paper and modded servers.

Note: You should always prefer server software such as Paper as it has a lot more customizable options and overall performance that data packs can never reach. You should only use this data pack if you have to use vanilla or you still have a lot performance issues.

## Credits
Originally made by E4ry, modified with their permission: ClearLag Datapack

Cleaner Armour Armor HUD Hotbar

Removes the Empty Armor Containers from the HUD, for a cleaner GUI:

vs Minecraft Vanilla:

Inspired by MC vanilla’s ‘Absorption Hearts’:

v1.20.2 (latest) and above is compatible with every other resourcepack.

Just select and put this resourcepack above others in order to work.

Circular Logs

# Improve the look of your default Logs with… ↴


## Adds Vanilla-like circulated Logs Top | No Optifine or other Mods needed!

### It’s supports every Version of the game! (even including Legacy ones)
### And day-by-day will have more and more mods supported!

Chroma Key – Green Screen

## Description

A vanilla shader that changes lime concrete to chroma key. Green screen instead of green concrete


## Dependencies
– Fabric loader requires Fabric API