Open 2.3.3: 2.3.5 Agricraft Sesame Seed not dropping produce

  • Thread starter Thread starter Hund_dk
  • Start date Start date
  • This section is closed. Please do bug reports over at the FTB GitHub repos.
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
H

Hund_dk

Guest
Version:
2.3.3

What is the bug:
Pam's HarvestCraft Crop Sesame does not give Sesame drops when used with Agricraft, the seed can be improved. (Note: Making Clippings and putting them into hotbar will make you'r minecraft crash when put in hand.)

Mod & Version:
Agricraft 1.7.10-1.4.6 & Pam's HarvestCraft 1.7.10k

Paste.feed-the-beast.com log:


Can it be repeated:
Yes, Plant Sesame Seed on Agricraft Crops and you won't get a produce drop when harvesting.

Known Fix:
Maybe needs to be added to mod/config.
 
can confirm, the same happens in my world, you're able to collect the seeds from sesame seeds, and improve them with agricraft, but they don't actually drop sesame seeds.
the same happens with gardens, you can keep harvesting the same garden that should drop sesame seeds, but they never do drop them.
 
You're going to have to bug Pam to correctly register the sesameseeds to the OreDict:
seed: <seedSesameSeeds>
fruit: <cropSesameSeeds> (instead of <cropSesameSeed>)
 
making a script with something like <cropSesameSeeds>.mirror(<cropSesameSeed>); should work right ?
 
I know i am kinda reviving this post after its been left alone for a month, but I discovered that you can use zzzzzz custom config's to add it to "cropSesameseed" (how all other crops work), it will actually drop sesame seeds.

Here is the exact code you would use for it
<ore>
<name>cropSesameseed</name>
<stack1>harvestcraft:sesameseedsItem 1 0</stack1>
</ore>
 
custom config is needed on both client and server sadly, but not sure about config file being needed or not.

*Just confirmed that the client only needs to add the mod and the config change is only needed server side, client side doesn't need that change.
 
Last edited: