WARNING: The mod can delay initial start of MC. Depends on the amount of blocks in your modpacks and the iteration in the config .
Changes in 1.14
~~~~~~~~~~~~~~~~~~~~~~
The Mod is required on the server now.
The drops are calculated during the start of the server. In singleplayer this happens when you join a world.
~~~~~~~~~~~~~~~~~~~~~~
The cache is in config/BlockDrops/blockdrops.txt.
- Can I use this in my mod pack?
- Yes.
Crash on startup on the latest 1.12 version:
// Hey, that tickles! Hehehe!
Time: 1/19/20 9:00 PM
Description: There was a severe problem during mod loading that has caused the game to fail
net.minecraftforge.fml.common.LoaderExceptionModCrash: Caught exception from Block Drops (blockdrops)
Caused by: java.lang.NullPointerException
at mrriegel.blockdrops.BlockDrops.lambda$postInit$2(BlockDrops.java:146)
at java.util.ArrayList.removeIf(Unknown Source)
at mrriegel.blockdrops.BlockDrops.postInit(BlockDrops.java:146)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraftforge.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:637)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:91)
at com.google.common.eventbus.Subscriber$SynchronizedSubscriber.invokeSubscriberMethod(Subscriber.java:150)
at com.google.common.eventbus.Subscriber$1.run(Subscriber.java:76)
at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:399)
at com.google.common.eventbus.Subscriber.dispatchEvent(Subscriber.java:71)
at com.google.common.eventbus.Dispatcher$PerThreadQueuedDispatcher.dispatch(Dispatcher.java:116)
at com.google.common.eventbus.EventBus.post(EventBus.java:217)
at net.minecraftforge.fml.common.LoadController.sendEventToModContainer(LoadController.java:219)
at net.minecraftforge.fml.common.LoadController.propogateStateMessage(LoadController.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:91)
at com.google.common.eventbus.Subscriber$SynchronizedSubscriber.invokeSubscriberMethod(Subscriber.java:150)
at com.google.common.eventbus.Subscriber$1.run(Subscriber.java:76)
at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:399)
at com.google.common.eventbus.Subscriber.dispatchEvent(Subscriber.java:71)
at com.google.common.eventbus.Dispatcher$PerThreadQueuedDispatcher.dispatch(Dispatcher.java:116)
at com.google.common.eventbus.EventBus.post(EventBus.java:217)
at net.minecraftforge.fml.common.LoadController.distributeStateMessage(LoadController.java:136)
at net.minecraftforge.fml.common.Loader.initializeMods(Loader.java:754)
at net.minecraftforge.fml.client.FMLClientHandler.finishMinecraftLoading(FMLClientHandler.java:336)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:535)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:378)
at net.minecraft.client.main.Main.main(SourceFile:123)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.multimc.onesix.OneSixLauncher.launchWithMainClass(OneSixLauncher.java:196)
at org.multimc.onesix.OneSixLauncher.launch(OneSixLauncher.java:231)
at org.multimc.EntryPoint.listen(EntryPoint.java:143)
at org.multimc.EntryPoint.main(EntryPoint.java:34)
So a small note for 1.14, if it's needed server side you can't have it call for JEI to be installed because JEI can't run server side (trust me I've done it by accident it just crashes). Just thought you should know.
Of course JEI runs server side. If you had a crash open an issue on JEI's github.
In reply to KidsDontPlay:
Okay, bit more testing and it works, some kind of conflict with something else... Either way it's hardly an "of course" with such minimal difference with it on server side and basically being designed as a client mod (same with NEI and even TMI). Still a really useful mod though.
In reply to N_Montana:
What ?
This is from JEI's FAQ :
Yes, with some features disabled
JEI isn't designed as a "client" mod. It can work in singleplayer/vanilla but it's designed as mod required by the server to provide information to the clients using it. It's definitely an "of course", before telling someone who's developing a companion mod to JEI that they're wrong about JEI, maybe make sure you didn't misunderstand something about it first, as a friendly reminder - no sarcasm.
Thanks for updating to 1.14, I couldn't wait to wait during worldgen again ! - totally worth the waiting time.
In reply to Shyning:
I like how you said it was required by the server after quoting an FAQ that said contrary. So your saying that JEI (a mod designed to view recipes and uses of all items and blocks) is designed to be specifically installed on a server and that having it work client side is a complete after thought? If there answer to "Can JEI run client-only or with a vanilla server?" is "Yes, with some features disabled" to me that sounds like they made everything that could work client-only work on client-only. You don't design a mod to work flawlessly client-side if it's required by the server. Now the reason you stated it was "required" (still love that) server side is "to provide information to the clients using it"... do you even know how tiny of detail that is? Sure it could be useful but it's hardly a required feature and since I can't find a lot of information of the other disabled "features" it hardly seems like it was designed as a server mod. Just as a small note NEI did control the usage of cheats and utilities through server side configuration but since this was more of a QOL thing than something you HAD to have I still think being designed as server side is a vast overstatement.
Now for the second part of my little rant "as a friendly reminder - no sarcasm" and then what I assume to be your attempt at some artificial sarcasm. First thing me and my family have the genetic mutations that cause psychopathy, sarcasm doesn't come naturally to me and serves no purpose in my opinion. Secondly I went on this mod page because of one fairly obvious reason: it peaked my interest. Now based of the simple fact that I replied to the mod authors comment should to your simple mind at least indicate some attempt at me wanting to use this mod thus me ending my comment with "Still a really useful mod though" shouldn't be held as sarcasm rather that I did not have time to write an essay about why I like this mod, but since people clearly don't understand that I guess I'm going to have to.
This mod fills in a gap in modded Minecraft that's been problematic from my experience with some mods requiring an item dropped by another block (first example I think of was Ex Nihilo (or Astris whichever) implementation of Thaumcraft infused shards where it had you break a block with the hammer to acquire the shard having this mod to actually say which block dropped which shard would have been a serious help. Also having the ability to see the drop chances and specifically the enchants that increases drops and by how much can help (to some extent) when planning on collecting resources in bulk.
In reply to N_Montana:
You really like to write a lot to tell few things, especially about "sarcasm" when I purposely said there was none in case the "friendly reminder" was understood as such.
When the FAQ mentions this question, it means this question got asked enough times/had enough confusion about it to be displayed there. Why ? Because JEI is shown as a mod working on the server-side (as well as client-side, which is cleared up in the FAQ). This point is written black on white, there isn't much more to tell about it. And I don't remember saying you didn't seem to need or like this mod in any shape or form ?
At least, your explanation of why this mod is a very welcome addition, is great.
In reply to N_Montana:
"You don't design a mod to work flawlessly client-side"
The text you guys are quoting expressly states that it doesn't work flawlessly client-side, though. It expressly says that only some of its capabilities function when purely clientside.
Does the cache need to be deleted if you later add/change mods or config that cause a change to drops? Maybe add that to the description.
In reply to CosmicDan:
Nevermind, checked the source myself - seems to detect blocks that are removed or added and will update the cache, but logic dictates that "automatic updating if a drop is changed" isn't possible because it would have to iterate every block to do that, making the whole idea of a cache redundant :)
I found incompatibility after update some mods.
https://pastebin.com/hy5Fkejp
(Forbiden Arcanus)
this works with other mods?
In reply to c_h_r_i_z_:
Any change this will support foragecraft drop data?
Great mod, thanks.
This is client side addon? Thanks in advance :)
In reply to Pyromanc3r:
Hi,
I really don't get it, how to use your mod and get the shown info's from the previews (can't find it in-game anywhere).
There is also no shortcut to display the block drops in the options.
Please provide more information how to get the results from the previews.
Version:
Thanks!
Bye
In reply to dRsrbZG:
In reply to MrRiegel:
Getting a client crash in stage 4 while loading up. Removing this mod allows me to load into the game.
crash report: https://pastebin.com/Zsbv2ry7