Set the weight to 0 in all the json files for the bow

Oct 13, 2025 by windailys.com 63 views

Introduction

In this article, we will be discussing a crash issue that occurs in NeoForge 1.21.1 when attempting to disable all standard tiers/pools. The crash is caused by an IllegalArgumentException: bound must be positive error, which is triggered when the weight of the tiers/pools is set to 0.

Reproducing the Crash

To reproduce the crash, follow these steps:

Copy mod jar datapack data files to kubejs\data: This step involves copying the necessary files from the mod jar to the kubejs data directory.
Set the weight to 0 in all the json files for the bow: This step involves modifying the json files in the data\tiered\tiered_modifiers\pools\bows and data\tiered\tiered_modifiers\tiers\bows directories to set the weight to 0.
Open game and load world: This step involves loading the world in the game.
Go into creative and grab a bow: This step involves entering creative mode and grabbing a bow.
Crash to desktop every time load world: This step involves loading the world and observing the crash.

Crash Report

The crash report is as follows:

// I let you down. Sorry :(

Time: 2025-03-12 21:21:01
Description: Ticking entity

java.lang.IllegalArgumentException: bound must be positive
	at java.base/java.util.Random.nextInt(Unknown Source) ~[?:?] {}
	at TRANSFORMER/unionlib@12.0.9/com.stereowalker.unionlib.util.GeneralUtilities.getRandomFrom(GeneralUtilities.java:20) ~[UnionLib-1.21.1-12.0.9-NeoForge-all.jar%23215!/:12.0.9] {re:classloading}
	at TRANSFORMER/tiered@1.0.5/com.stereowalker.tiered.api.ModifierUtils.getRandomAttributeIDFor(ModifierUtils.java:26) ~[Reforged-1.21.1-1.0.5-NeoForge.jar%23211!/:unspecified] {re:mixin,re:classloading}
	at TRANSFORMER/tiered@1.0.5/com.stereowalker.tiered.Reforged.attemptToAffixTier(Reforged.java:235) ~[Reforged-1.21.1-1.0.5-NeoForge.jar%23211!/:unspecified] {re:mixin,re:classloading}
	at java.base/java.lang.Iterable.forEach(Unknown Source) ~[?:?] {re:computing_frames,re:mixin}
	at TRANSFORMER/tiered@1.0.5/com.stereowalker.tiered.Reforged.lambda$registerInserts$8(Reforged.java:168) ~[Reforged-1.21.1-1.0.5-NeoForge.jar%23211!/:unspecified] {re:mixin,re:classloading}
	at TRANSFORMER/unionlib@12.0.9/com.stereowalker.unionlib.insert.handler.living.LivingInsertHandler.lambda$insert$0(LivingInsertHandler.java:11) ~[UnionLib-1.21.1-12.0.9-NeoForge-all.jar%23215!/:12.0.9] {re:classloading}
	at java.base/java.util.ArrayList.forEach(Unknown Source) ~[?:?] {re:mixin}
	at TRANSFORMER/unionlib@12.0.9/com.stereowalker.unionlib.insert.InsertHandler.loopThrough(InsertHandler.java:8) ~[UnionLib-1.21.1-12.0.9-NeoForge-all.jar%23215!/:12.0.9] {re:classloading}
	at TRANSFORMER/unionlib@12.0.9/com.stereowalker.unionlib.insert.handler.living.LivingInsertHandler.insert(LivingInsertHandler.java:10) ~[UnionLib-1.21.1-12.0.9-NeoForge-all.jar%23215!/:12.0.9] {re:classloading}
	at TRANSFORMER/unionlib@12.0.9/com.stereowalker.unionlib.neoforge.PlatformHelper.lambda$handleEvents$19(PlatformHelper.java:159) ~[UnionLib-1.21.1-12.0.9-NeoForge-all.jar%23215!/:12.0.9] {re:classloading}
	at MC-BOOTSTRAP/net.neoforged.bus/net.neoforged.bus.ConsumerEventHandler.invoke(ConsumerEventHandler.java:26) ~[bus-8.0.2.jar%23145!/:?] {}
	at MC-BOOTSTRAP/net.neoforged.bus/net.neoforged.bus.EventBus.post(EventBus.java:350) ~[bus-8.0.2.jar%23145!/:?] {}
	at MC-BOOTSTRAP/net.neoforged.bus/net.neoforged.bus.EventBus.post(EventBus.java:315) ~[bus-8.0.2.jar%23145!/:?] {}
	at TRANSFORMER/neoforge@21.1.133/net.neoforged.neoforge.event.EventHooks.fireEntityTickPost(EventHooks.java:944) ~[neoforge-21.1.133-universal.jar%23198!/:?] {re:classloading}
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.server.level.ServerLevel.tickNonPassenger(ServerLevel.java:775) ~[client-1.21.1-20240808.144430-srg.jar%23197!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:kubejs.mixins.json:ServerLevelMixin from mod kubejs,pl:mixin:A}
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.world.level.Level.guardEntityTick(Level.java:570) ~[client-1.21.1-20240808.144430-srg.jar%23197!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:kubejs.mixins.json:LevelMixin from mod kubejs,pl:mixin:A}
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.server.level.ServerLevel.lambda$tick$2(ServerLevel.java:420) ~[client-1.21.1-20240808.144430-srg.jar%23197!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:kubejs.mixins.json:ServerLevelMixin from mod kubejs,pl:mixin:A}
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.world.level.entity.EntityTickList.forEach(EntityTickList.java:54) ~[client-1.21.1-20240808.144430-srg.jar%23197!/:?] {re:classloading}
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.server.level.ServerLevel.tick(ServerLevel.java:400) ~[client-1.21.1-20240808.144430-srg.jar%23197!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:kubejs.mixins.json:ServerLevelMixin from mod kubejs,pl:mixin:A}
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.server.MinecraftServer.tickChildren(MinecraftServer.java:1037) ~[client-1.21.1-20240808.144430-srg.jar%23197!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:A}
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:917) ~[client-1.21.1-20240808.144430-srg.jar%23197!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:A}
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.client.server.IntegratedServer.tickServer(IntegratedServer.java:110) ~[client-1.21.1-20240808.144430-srg.jar%23197!/:?] {re:classloading,pl:runtimedistcleaner:A}
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:707) ~[client-1.21.1-20240808.144430-srg.jar%23197!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:A}
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.server.MinecraftServer.lambda$spin$2(MinecraftServer.java:267) ~[client-1.21.1-20240808.144430-srg.jar%23197!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:A}
	at java.base/java.lang.Thread.run(Unknown Source) [?:?]<br/>
# NeoForge 1.21.1 Crash: IllegalArgumentException: bound must be positive - Q&A

## Introduction

In our previous article, we discussed a crash issue that occurs in NeoForge 1.21.1 when attempting to disable all standard tiers/pools. The crash is caused by an `IllegalArgumentException: bound must be positive` error, which is triggered when the weight of the tiers/pools is set to 0. In this article, we will answer some frequently asked questions related to this issue.

## Q: What is the cause of the crash?

A: The crash is caused by an `IllegalArgumentException: bound must be positive` error, which is triggered when the weight of the tiers/pools is set to 0.

## Q: How can I reproduce the crash?

A: To reproduce the crash, follow these steps:

1. **Copy mod jar datapack data files to kubejs\data**: This step involves copying the necessary files from the mod jar to the kubejs data directory.
2. **Set the weight to 0 in all the json files for the bow**: This step involves modifying the json files in the `data\tiered\tiered_modifiers\pools\bows` and `data\tiered\tiered_modifiers\tiers\bows` directories to set the weight to 0.
3. **Open game and load world**: This step involves loading the world in the game.
4. **Go into creative and grab a bow**: This step involves entering creative mode and grabbing a bow.
5. **Crash to desktop every time load world**: This step involves loading the world and observing the crash.

## Q: What is the solution to the crash?

A: The solution to the crash is to set the weight of the tiers/pools to a positive value instead of 0.

## Q: How can I set the weight of the tiers/pools to a positive value?

A: To set the weight of the tiers/pools to a positive value, follow these steps:

1. **Open the json files for the bow**: This step involves opening the json files in the `data\tiered\tiered_modifiers\pools\bows` and `data\tiered\tiered_modifiers\tiers\bows` directories.
2. **Change the weight to a positive value**: This step involves modifying the weight value in the json files to a positive value.
3. **Save the changes**: This step involves saving the changes to the json files.

## Q: What are the benefits of setting the weight of the tiers/pools to a positive value?

A: Setting the weight of the tiers/pools to a positive value allows you to disable the standard tiers/pools without causing a crash.

## Q: Are there any other solutions to the crash?

A: Yes, there are other solutions to the crash. You can try the following:

1. **Update the mod to the latest version**: This step involves updating the mod to the latest version to see if the issue has been fixed.
2. **Disable the mod**: This step involves disabling the mod to see if it is causing the issue.
3. **Contact the mod author**: This step involves contacting the mod author to see if they can provide a solution to the issue.

## Q: How can I prevent the crash from occurring in the future?

A: To prevent the crash from occurring in the future, follow these steps:

1. **Set the weight of the tiers/pools to a positive value**: This step involves setting the weight of the tiers/pools to a positive value instead of 0.
2. **Update the mod to the latest version**: This step involves updating the mod to the latest version to see if the issue has been fixed.
3. **Disable the mod**: This step involves disabling the mod to see if it is causing the issue.

## Q: What are the system requirements for NeoForge 1.21.1?

A: The system requirements for NeoForge 1.21.1 are:

* **Operating System**: Windows 10 or later
* **Processor**: Intel Core i5 or AMD equivalent
* **Memory**: 8 GB RAM or more
* **Graphics**: NVIDIA GeForce GTX 1060 or AMD equivalent
* **Storage**: 10 GB available space or more

## Q: How can I contact the mod author?

A: To contact the mod author, follow these steps:

1. **Visit the mod website**: This step involves visiting the mod website to see if there is a contact form or email address.
2. **Check the mod forums**: This step involves checking the mod forums to see if there are any threads related to the issue.
3. **Contact the mod author directly**: This step involves contacting the mod author directly through email or social media.