Gear decision
I am choosing what to wear or enchant
Start with items and enchantments, then run the exact incoming hit through the armor model.
Reference desk / mechanics before guesses
Find the category that changes your next move, check edition-sensitive details, and continue into a guide or tool when a static reference is no longer enough.
Identify
The object or system
Check
Version and edition
Decide
What changes next
Apply
Guide or tool
Reference areas
These links describe the content that is actually available. There are no inflated database totals or decorative “popular” rankings.
Blocks
Compare natural, crafted, decorative, utility, and redstone blocks by the job they perform.
Items
Review equipment, resources, food, drops, and progression items before using a rare material.
Mobs
Use behavior, spawn context, drops, and combat notes to choose the right response.
Biomes
Compare climate, terrain, resources, structures, and notable spawns without pretending a biome list can locate a seed.
Structures
Review risk, navigation, useful loot, and the reason to visit before committing to the route.
Enchantments
Check eligible gear, maximum levels, conflicts, and the role each enchantment serves in a complete setup.
Status Effects
Search positive, harmful, neutral, command, potion, beacon, raid, and trial effects with edition caveats.
Continue the answer
Reference pages work best as the first step. These routes connect a mechanic to the guide or calculator that can finish the job.
Gear decision
Start with items and enchantments, then run the exact incoming hit through the armor model.
Exploration decision
Read the environment and destination first, then plan coordinates and supplies around the actual trip.
System decision
Identify the block and mob behavior involved, then move to a guide or simulator for the sequence.
How to use this hub
Start with the decision you need to make. A block, item, or mob page is useful only when it changes that decision.
Java and Bedrock can differ in combat, spawning, redstone, commands, and availability. Treat edition notes as part of the mechanic.
Use a reference to choose valid inputs, then use a calculator or planner for the scenario-specific answer.
Keep the reference useful
Include the page, edition, game version, and the mechanic that appears wrong. Specific corrections are easier to verify and maintain.