Core Data
The core customization component is responsible for defining four key aspects of nearly every bee imaginable:
the flower(s) which a bee uses for pollination
the base amount of time the bee spends in the hive
associated lore
the honeycombs produced, if any
Identifier
The root JSON of the core customization component looks like this:
The identifier of the component is as such:
Customization Options
honeycombVariation
honeycombVariation
The identifier of the honeycomb variation produced by the bee. More information about honeycomb variation can be found in the Custom Honeycombs section.
Name: Honeycomb Variation
Key: honeycombVariation
Type: String
Default: No Honeycomb
flower
flower
Specifies what flower(s) the bee can pollinate. With the use of Miscellaneous, the syntax will vary based on the definition. The flower can be defined as a tag, a list of blocks, or a single block. See the examples below for further understanding.
entityFlower
entityFlower
When the flower a bee can pollinate is an entity, entityflower
must be used instead. The syntax used remains the same as blocks. See the examples below for further understanding.
maxTimeInHive
maxTimeInHive
The base amount of time a bee spends in a hive. This value is modified based on the hive tier.
Name: Max Time in Hive
Key: maxTimeInHive
Type: Integer
Range: ≥600
Default: 2400
lore
lore
Lore is cosmetic text displayed in JEI tooltips when hovering over the bee with the cursor. It can be extremely useful for providing players with hints on how to obtain the bee or it can be useful for memes and credits.
Last updated